Parallel Execution In A Transaction Using Independent Queries

• US 20130166523A1
• Filed: 12/21/2011
• Published: 06/27/2013
• Est. Priority Date: 12/21/2011
• Status: Abandoned Application

• Current Assignee: Sybase Incorporated (SAP SE)
• Original Assignee: Sybase Incorporated (SAP SE)
• Inventors: PATHAK, Amit, Sayyaparaju, Sunil, Mittal, Rahul
• Application Number:
  US13/332,483
• Publication Number:
  US 20130166523A1
• Time in Patent Office: Days
• US Class Current: 707/703
• CPC Class Codes: G06F 9/466 Transaction processing

Abstract

Embodiments include a method, apparatus and computer program product for executing a database transaction in parallel using subtransactions. The method includes receiving a transaction at an application, the transaction having a first statement and a second statement, and determining whether operation of the first statement is independent from operation of the second statement. When it is determined that operation of the first statement is independent from operation of the second statement, assigning the first statement to a first subtransaction and the second statement to a second subtransaction, the first and second subtransactions being part of a transaction group. The method further includes executing the subtransactions using resources of the database. Finally, when execution of all of the subtransactions have successfully completed, committing all of the subtransactions.

Claims

1. A method of executing a database transaction in parallel using subtransactions, comprising:

receiving a transaction at an application, wherein the transaction has a first statement and a second statement;

determining whether operation of the first statement is independent from operation of the second statement;

when it is determined that operation of the first statement is independent from operation of the second statement, assigning the first statement to a first subtransaction and the second statement to a second subtransaction, wherein the first and second subtransactions are part of a transaction group;

performing coordinated execution of the transaction group using resources of a database; and

when coordinated execution of all of the subtransactions of the transaction group has successfully completed, the subtransactions are committed.

2. The method of claim 1, wherein receiving a transaction at an application comprises receiving a transaction at a database client coupled to the database.

3. The method of claim 1, wherein receiving a transaction at an application comprises receiving a transaction at a database from a database client.

4. The method of claim 1, wherein determining based on the defining statement comprises determining based on a structured query language (SQL) statement, and receiving a transaction having a first statement and a second statement comprises receiving a transaction having a first SQL statement and a second SQL statement.

5. The method of claim 1, wherein executing the subtransactions using resources of the database comprises protecting the execution of the subtransactions from being deadlocked during execution using resources of the database.

6. The method of claim 1, further comprising, when the first subtransaction in the transaction group satisfies a first condition, rolling back all subtransactions in the transaction group.

7. The method of claim 6, wherein the first subtransaction satisfying the first condition comprises the first subtransaction failing to execute.

8. The method of claim 6, wherein the first subtransaction satisfying the first condition comprises the first subtransaction issuing a request for a lock that is held by the second subtransaction.

9. The method of claim 6, wherein rolling back all subtransactions in the transaction group comprises rolling back all subtransactions in the transaction group based on a database log of the database.

10. The method of claim 1, wherein assigning the first statement to a first subtransaction and the second statement to a second subtransaction comprises assigning the first statement to a controlling subtransaction and the second statement to a member subtransaction.

11. The method of claim 10, wherein upon a recovery event, the controlling subtransaction is successfully committed or rolled back before a process to commit or rollback the member subtransaction is commenced.

12. The method of claim 10, wherein upon a recovery event where the member transaction is unfinished, the member transaction is recovered based on a final state of the controlling subtransaction.

13. The method of claim 12, wherein, the member transaction is recovered based on a final state of the controlling subtransaction comprises recovering the member transaction based on the final state of the controlling transaction as indicated by a database log.

14. An application configured to parallel execute a database transaction using subtransactions, comprising:

a transaction receiver configured to receive a database transaction having a first statement and a second statement;

an independence determiner configured to determine whether operation of the first statement is independent from operation of the second statement;

a subtransaction creator configured to, when it is determined that operation of the first statement is independent from operation of the second statement, assign the first statement to a first subtransaction and the second statement to a second subtransaction, wherein the first and second subtransactions are part of a transaction group; and

a database engine configured to;

parallel execute the subtransactions, and

when execution of all of the subtransactions have successfully completed, commit all of the subtransactions.

15. The application of claim 14, wherein the independence determiner is configured to determine that operation of the first statement is independent from operation of the second statement based on a defining statement that is a structured query language (SQL) statement, and wherein the transaction receiver is further configured to receive a database transaction having a first SQL statement and a second SQL statement.

16. The application of claim 15, wherein the database engine is further configured to protect the execution of the subtransactions from being deadlocked during execution.

17. The application of claim 14, wherein the database engine is further configured to, when the first subtransaction in the transaction group satisfies a first condition, roll back all subtransactions in the transaction group.

18. The application of claim 17, wherein the first condition comprises the first subtransaction failing to execute.

19. The of claim 17, wherein the first condition comprises the first subtransaction issuing a request for a lock that is held by the second subtransaction.

20. The of claim 17, wherein the first condition comprises the first subtransaction issuing a request for a lock that is held by a statement upon which the second subtransaction depends.

21. The database of claim 17, wherein the database engine is further configured to roll back a subtransaction in the transaction group based a database log of the database.

22. A computer-readable medium having computer-executable instructions stored thereon that, when executed by a computing device, cause the computing device to perform a method of executing a database transaction in parallel using subtransactions, the instructions comprising:

receiving a transaction at an application, wherein the transaction has a first statement and a second statement;

determining whether operation of the first statement is independent from operation of the second statement;

when it is determined that operation of the first statement is independent from operation of the second statement, assigning the first statement to a first subtransaction and the second statement to a second subtransaction, wherein the first and second subtransactions are part of a transaction group;

performing coordinated execution of the transaction group using resources of a database; and

when coordinated execution of all of the subtransactions of the transaction group has successfully completed, the subtransactions are committed.