Techniques for implementing batch processing in a database system

• US 9,275,098 B2
• Filed: 06/12/2013
• Issued: 03/01/2016
• Est. Priority Date: 08/25/2008
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Yancey, Scott, Smith, Andrew, Waite, Andrew, Weissman, Craig
• Primary Examiner(s): Casanova, Jorge A
• Application Number:
  US13/916,457
• Publication Number:
  US 20130318057A1
• Time in Patent Office: 993 Days
• Field of Search: 707/613, 707/702, 707/703
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/2372 Updates performed during offline database operations
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation

Abstract

In accordance with embodiments, there are provided techniques for implementing batch processing in a multi-tenant database system. These techniques for implementing batch processing in a multi-tenant database system may enable embodiments to provide great flexibility to a tenant of the architecture to perform desired functions on content of the database while allowing the owner of the architecture schedule the processing of the functions on the content.

Claims

1. A method comprising:

receiving a request for processing against a database system;

enqueuing a batch request in a request queue responsive to receiving the request;

calling a query locator object that points to a maximum number of objects to be scheduled for uninterrupted processing in a single batch process against the database system to ensure that the single batch process does not consume in excess of a threshold amount of resources of the database system;

retrieving the maximum number of objects based on the called query locator object;

scheduling execution of the batch request to be executed via uninterrupted processing during the single batch process by queuing the batch request in an execute queue amongst a plurality of other objects in the execute queue;

executing the batch request against the database system; and

sending notification to users indicating completion of the execution of the batch request against the database system.

2. The method of claim 1:

wherein a START method identifies the maximum number of objects to be scheduled for uninterrupted processing as a full set of objects for the batch request.

3. The method of claim 1:

wherein a QueryLocator object points to the maximum number of objects to be scheduled for uninterrupted processing via a server side database cursor persisted on architecture implementing the database system.

4. The method of claim 3:

wherein the maximum number of objects to be scheduled for uninterrupted processing comprises a quantity defined via the architecture based at least in part on processing capacity the architecture and/or a priori information concerning consumption history of the resources of the architecture.

5. The method of claim 3:

wherein the maximum number of objects to be scheduled for uninterrupted processing is determined at least in part by dynamically monitoring other processes executing via the architecture and including a priori information about particular times during which consumption of resources of the architecture has historically been reduced.

6. The method of claim 1:

wherein scheduling execution of the batch request to be executed comprises identifying objects to be subjected to an EXECUTE method; and

wherein identifying the objects comprises iteratively calling a QUERYMORE method to determine whether additional sub-groups of objects are to be included in a set of objects to be subjected to the EXECUTE method until it is determined that no additional sub-groups of objects are to be subjected to the EXECUTE method.

7. The method of claim 1, wherein scheduling execution of the batch request to be executed via uninterrupted processing during the single batch process comprises reducing computational load on the database system by holding execution of batch processes until a later time.

8. The method of claim 1:

wherein the database system comprises a multi-tenant on-demand database system having elements of hardware and software shared multiple user tenants of the database system.

9. The method of claim 1:

wherein receiving the request comprises receiving the request at one of a plurality of batch code interfaces, wherein user tenants of the database system queue request queue for batch processing; and

wherein each of the plurality of batch code interfaces are prevented from having methods associated therewith invoked for a length of time or number of process cycles or consume in excess of the threshold amount of the resources of the database system.

10. The method of claim 9, wherein the batch code interfaces are executed asynchronously with operations of the database system by invoking multiple methods of the batch code interfaces to provide batch processing facilities to users of the database system.

11. Non-transitory computer readable storage media having instructions stored thereupon that, when executed by a processor of an application hosting service, the processor causes the application hosting service to perform operations comprising:

receiving a request for processing against a database system;

enqueuing a batch request in a request queue responsive to receiving the request;

calling a query locator object that points to a maximum number of objects to be scheduled for uninterrupted processing in a single batch process against the database system to ensure that the single batch process does not consume in excess of a threshold amount of resources of the database system;

retrieving the maximum number of objects based on the called query locator object;

scheduling execution of the batch request to be executed via uninterrupted processing during the single batch process by queuing the batch request in an execute queue amongst a plurality of other objects in the execute queue;

executing the batch request against the database system; and

sending notification to users indicating completion of the execution of the batch request against the database system.

12. The non-transitory computer readable storage media of claim 11:

wherein a START method identifies the maximum number of objects to be scheduled for uninterrupted processing as a full set of objects for the batch request.

13. The non-transitory computer readable storage media of claim 11:

wherein a QueryLocator object points to the maximum number of objects to be scheduled for uninterrupted processing via a server side database cursor persisted on architecture implementing the database system.

14. The non-transitory computer readable storage media of claim 13:

wherein the maximum number of objects to be scheduled for uninterrupted processing comprises a quantity defined via the architecture based at least in part on processing capacity the architecture and/or a priori information concerning consumption history of the resources of the architecture.

15. The non-transitory computer readable storage media of claim 13:

wherein the maximum number of objects to be scheduled for uninterrupted processing is determined at least in part by dynamically monitoring other processes executing via the architecture and including a priori information about particular times during which consumption of resources of the architecture has historically been reduced.

16. The non-transitory computer readable storage media of claim 11:

wherein scheduling execution of the batch request to be executed comprises identifying objects to be subjected to an EXECUTE method; and

wherein identifying the objects comprises iteratively calling a QUERYMORE method to determine whether additional sub-groups of objects are to be included in a set of objects to be subjected to the EXECUTE method until it is determined that no additional sub-groups of objects are to be subjected to the EXECUTE method.

17. The non-transitory computer readable storage media of claim 11,

wherein scheduling execution of the batch request to be executed via uninterrupted processing during the single batch process comprises reducing computational load on the database system by holding execution of batch processes until a later time.

18. The non-transitory computer readable storage media of claim 11:

wherein receiving the request comprises receiving the request at one of a plurality of batch code interfaces, wherein user tenants of the database system queue request queue for batch processing; and

wherein each of the plurality of batch code interfaces are prevented from having methods associated therewith invoked for a length of time or number of process cycles or consume in excess of the threshold amount of the resources of the database system.

19. The non-transitory computer readable storage media of claim 18,

wherein the batch code interfaces are executed asynchronously with operations of the database system by invoking multiple methods of the batch code interfaces to provide batch processing facilities to users of the database system.

20. A system comprising:

a processor; and

a memory;

a database system;

a batch interface to receive a request for processing against the database system;

a request queue to enqueue a batch request responsive to receiving the request;

a query locator object to point to a maximum number of objects to be scheduled for uninterrupted processing in a single batch process against the database system to ensure that the single batch process does not consume in excess of a threshold amount of resources of the database system;

a START method to retrieve the maximum number of objects based on the called query locator object and schedule execution of the batch request to be executed via uninterrupted processing during the single batch process by queuing the batch request in an execute queue amongst a plurality of other objects in the execute queue;

an EXECUTE method to execute the batch request against the database system; and

a FINISH method to send notification to users indicating completion of the execution of the batch request against the database system.