Salesforce, Inc.

Salesforce Com, Inc.

Randy Philip Spalten

Simon Y Wong

Jeffrey Ira Cohen

Jameison Bear Martin

Gary J Baker

Nathaniel Wyatt

Serge Philippe Rielau

Douglas Doole

Abhijith Anilkumar

Stephane Geneix

Techniques are disclosed relating to implementing a statement-level INSTEAD OF trigger. In one embodiment a computer system stores trigger information associated with a statement-level database trigger executable to initiate execution of at least one trigger instruction for a database instead of performing a particular database operation, on a database view, specified by a database operation statement. The computer system receives a first database operation statement specifying performance of the particular database operation on the database view and identifies a set of target rows, within the database view, targeted by the first database operation statement. In addition, the computer system generates a reference table associated with the database view, where the reference table includes rows corresponding to the target rows. The computer system executes the statement-level database trigger instead of executing the database operation statement, where executing the statement-level database trigger includes accessing the reference table.

Statement-level instead-of database triggers

The present disclosure is directed to updating a multi-tenant database concurrent with tenant cloning. In some embodiments, a computer system receives a request to perform an update operation on a multi-tenant database. The update operation includes updating database entries for a plurality of tenants. Responsive to receiving the request, the update operation is initiated. Performing the update operation includes accessing a list identifying database entries awaiting the updating. During the accessing of the list, the update operation holds a lock. When the lock becomes available for acquisition, a clone process is permitted to create, during performance of the update operation, a clone of a tenant's data within the database.

Updating a multi-tenant database concurrent with tenant cloning

System and methods are provided for creating a tenant of a database system, the tenant to have tenant data stored in an immutable storage of the database system associated with a tenant identifier. A request may be received at the database system to create a new tenant. A template tenant metadata of a template tenant may be selected at the database system to create the new tenant based on the received request. A new tenant identifier may be created at the database system based on the selected template tenant metadata. The new tenant may be created by associating the new tenant identifier with a snapshot of at least a portion of the template tenant metadata at a point in time when the template tenant metadata is made accessible to the new tenant. Systems and methods are also provided for removing a tenant of a database system by removing references to a tenant identifier.

Systems and methods of creation and deletion of tenants within a database

Techniques are disclosed for handling database queries from multiple different application versions using a single database. A computer system executing a database management system (DBMS) may receive a database query for a database, where the database query is received from a particular version of an application having a plurality of versions. The database query may specify the particular version. The computer system may then identify catalog tables, where the catalog tables include version information columns storing version access information. The computer system may determine that version access information for the database query indicates that one or more database objects corresponding to the database query are accessible to the particular version of the application. Based on the determining, the computer system may access one or more database objects that are responsive to the database query and are accessible to the particular version of the application, which may advantageously reduce or avoid duplication of data stored in the database.

Database implementation for different application versions

Growing community of inventors

Benicia, CA, United States of America

Randy Philip Spalten