Methods and systems for deleting large amounts of data from a multitenant database

• US 8,635,250 B2
• Filed: 04/26/2011
• Issued: 01/21/2014
• Est. Priority Date: 04/26/2010
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Mehra, Vinod
• Primary Examiner(s): PENG, HUAWEN A
• Application Number:
  US13/094,745
• Publication Number:
  US 20110264704A1
• Time in Patent Office: 1,001 Days
• Field of Search: 707/802
• US Class Current: 707/802
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: G06F 16/289 Object oriented databases

Abstract

A bulk delete for remote database access is provided. A delete request is received over an API for a multitenant database. The delete can be for either a soft delete or a hard delete, where hard delete allows the system to skip use of a recycle bin. Multiple batch jobs are created to implement the delete request, and the batch jobs are executed asynchronously with respect to the request until the request is satisfied. Results for each batch job can be stored and provided to a client to indicate results of the delete operation.

Claims

1. A system comprising:

a multitenant database including hardware and software components to implement a database shared by a plurality of separate and distinct customer organizations,

wherein the multitenant database stores data for multiple client organizations each identified by a tenant identifier (ID) and one or more users are associated with the tenant ID,

wherein the one or more users of each client organization accesses data identified by the tenant ID associated with the respective client organization, and

wherein the multitenant database is hosted by an entity separate from the client organization; and

a server coupled to the multitenant database, the server to receive a delete request from a client at an application server via a web services application program interface (API) in a multitenant database, the delete request to delete multiple entries of the multitenant database, the delete request including a tenant ID to identify a tenant associated with the delete request;

determine whether the delete request is for a soft delete or a hard delete;

create multiple batch jobs to implement a delete job for the determined delete request in response to receiving the request, each batch job to perform a delete operation to delete one or more entries;

register the delete job with a scheduler of the multitenant database, each of the batch jobs to execute under the registered delete job, the scheduler to schedule batch jobs for one or more application servers to implement the delete job;

the multitenant database to further execute the batch jobs on the one or more application servers to execute the delete operations to implement the delete job asynchronously with respect to receiving the delete request, where each application server references the delete job with the multitenant database when it executes its batch jobs; and

receive results for each executed batch job from the database until the delete job is completed.

2. The system of claim 1, wherein the server is a first server, and further comprising:

a second server to execute at least one batch job to implement the delete job;

wherein the first server is to execute the batch jobs at least by sending a batch job to the second server for execution.

3. The system of claim 1, wherein the server determines the request is a soft delete request, and the server is to execute the batch jobs by deleting the entries with a soft delete, where the entries can be undeleted within a threshold amount of time, after which they are automatically physically deleted.

4. The system of claim 1, wherein the server determines the request is a hard delete request, and the server is to execute the batch jobs by deleting the entries with a hard delete, where there is no threshold amount of time where the entries can be undeleted, and the entries are physically deleted at a next execution of a hard delete process.

5. A method comprising:

receiving a delete request from a client at an application server via a web services application program interface (API) in a multitenant database, the delete request to delete multiple entries of the multitenant database, the delete request including a tenant identifier (ID) to identify a tenant associated with the delete request, the tenant being one of multiple client organizations having data stored in the multitenant database;

determining whether the delete request is for a soft delete or a hard delete;

creating multiple batch jobs to implement a delete job for the determined delete request in response to receiving the request, each batch job to perform a delete operation to delete one or more entries;

registering the delete job with a scheduler of the multitenant database, each of the batch jobs to execute under the registered delete job, the scheduler to schedule batch jobs for one or more application servers to implement the delete job;

executing the batch jobs on the one or more application servers to execute the delete operations to implement the delete job asynchronously with respect to receiving the delete request, where each application server references the delete job with the multitenant database when it executes its batch jobs; and

storing results for each executed batch job until the delete job is completed.

6. The method of claim 5, wherein the delete request identifies the multiple entries and a tenant identifier of the multitenant database.

7. The method of claim 5, wherein executing the batch jobs comprises executing at least one batch job on an application server other than the application server that received delete request from the client.

8. The method of claim 5, wherein executing the batch jobs comprises executing at least one of the batch jobs on an application server other than the application server that received the delete request from the client.

9. The method of claim 5, wherein executing the batch jobs further comprises:

deleting the entries with a soft delete, where the entries can be undeleted within a threshold amount of time, after which they are automatically physically deleted.

10. The method of claim 5, where executing the batch jobs further comprises:

deleting the entries with a hard delete, where there is no threshold amount of time where the entries can be undeleted, and the entries are physically deleted at a next execution of a hard delete process.

11. The method of claim 5, further comprising:

providing the results to the client in response to a poll request by the client.

12. An article of manufacture comprising a computer readable storage medium having content stored thereon, which when executed, cause a machine to perform operations including:

receiving a delete request from a client at an application server via a web services application program interface (API) in a multitenant database, the delete request to delete multiple entries of the multitenant database, the delete request including a tenant identifier (ID) to identify a tenant associated with the delete request, the tenant being one of multiple client organizations having data stored in the multitenant database;

determining whether the delete request is for a soft delete or a hard delete;

creating multiple batch jobs to implement a delete job for the determined delete request in response to receiving the request, each batch job to perform a delete operation to delete one or more entries;

registering the delete job with a scheduler of the multitenant database, each of the batch jobs to execute under the registered delete job, the scheduler to schedule batch jobs for one or more application servers to implement the delete job;

executing the batch jobs on the one or more application servers to execute the delete operations to implement the delete job asynchronously with respect to receiving the delete request, where each application server references the delete job with the multitenant database when it executes its batch jobs; and

storing results for each executed batch job until the delete job is completed.

13. The article of manufacture of claim 12, where the content to provide instructions for executing the batch jobs comprises content to provide instructions for executing at least one batch job on an application server other than the application server that received delete request from the client.

14. The article of manufacture of claim 12, wherein the content to provide instructions for executing the batch jobs comprises content to provide instructions for executing at least one of the batch jobs on an application server other than the application server that received the delete request from the client.

15. The article of manufacture of claim 12, wherein the content to provide instructions for executing the batch jobs further comprises content to provide instructions for deleting the entries with a soft delete, where the entries can be undeleted within a threshold amount of time, after which they are automatically physically deleted.

16. The article of manufacture of claim 12, wherein the content to provide instructions for executing the batch jobs further comprises content to provide instructions for deleting the entries with a hard delete, where there is no threshold amount of time where the entries can be undeleted, and the entries are physically deleted at a next execution of a hard delete process.