System and Method for Subunit Operations in a Database

• US 20110029498A1
• Filed: 07/09/2010
• Published: 02/03/2011
• Est. Priority Date: 07/10/2009
• Status: Active Grant

• Current Assignee: Teradata US, Inc. (Teradata Corporation)
• Original Assignee: xkoto, Inc. (Teradata Corporation)
• Inventors: Wang, Yi, Ferguson, Gregory Paul, Heisz, Jeffrey Maurice, Ta-Min, Richard, Daljevic, Branko
• Granted Patent: US 8,209,699 B2
• Time in Patent Office: Days
• US Class Current: 707/703
• CPC Class Codes: G06F 16/2343 Locking methods, e.g. distributed locking or locking implementation details
• CPC Class Codes: G06F 16/2471 Distributed queries

Abstract

A method for processing a transaction request at a database load balancer is disclosed. The method comprises receiving the transaction request, where the transaction request is comprised of one or more operations to be performed upon a database; analyzing the transaction request to determine the one or more operations; analyzing the transaction to determine one or more database units associated with the operations; analyzing the transaction requests and the one or more database units to determine one or more database subunits associated with the database units that the transaction request will perform one or more operations upon; associating one or more database locks with each of the one or more operations; analyzing one or more of the database locks to determine one or more sequence numbers associated with each of the one or more operations; and transmitting one or more unique identifiers for each of the database subunits, the one or more operations with the associated database locks and the sequence numbers to one or more database servers accessible to the database load balancer. Systems, apparatus and computer programming associated with or implementing the method are also disclosed.

Claims

1. A method for processing a transaction request at a database load balancer, the method comprising:

(a) receiving the transaction request, where the transaction request is comprised of one or more operations to be performed upon a database;

(b) analyzing the transaction request to determine the one or more operations and to determine one or more database units associated with the operations;

(c) analyzing the transaction requests and the one or more database units to determine one or more database subunits associated with the database units that the transaction request will perform one or more operations upon;

(d) associating one or more database locks with each of the one or more operations;

(e) analyzing one or more of the database locks to determine one or more sequence numbers associated with each of the one or more operations; and

(f) transmitting the one or more operations with the one or more unique identifiers for each of the database subunits, the database locks and the sequence numbers to one or more database servers accessible to the database load balancer.

2. The method of claim 1, wherein the one or more operations are selected from the group consisting essentially of:

modifying option settings, read operations, select operations, write operations, commit operations, roll back operations, execute operations, and prepare operations.

3. The method of claim 1, wherein each of the one or more locks has associated with it a lock number, lock type, lock scope and lock sequence.

4. The method of claim 3 further comprising the step of determining a transaction isolation level associated with the transaction request.

5. The method of claim 4 wherein each lock scope is based on the transaction isolation level.

6. The method of claim 5, wherein each lock scope is based on the database subunit.

7. The method of claim 3 wherein the lock scope is further based on the lock type.

8. A method of processing a transaction request at a database load balancer, the method comprising:

(a) receiving the transaction request, where the transaction is comprised of one or more operations to be performed upon a database;

(b) analyzing the transaction request to determine the one or more scripts to be executed through a scripting module;

(c) determining through the scripting module and associated scripts, the one or more operations, the one or more database units associated with the database record, the one or more database subunits associated with each database unit and the one or more locks with the one or more operations;

(d) analyzing the one or more database locks to determine one or more sequence numbers associated with each of the one or more operations; and

(e) transmitting the one or more operations with the one or more unique identifiers for each of the database subunits, the associated database locks and the sequence numbers to one or more database servers accessible to the database load balancer.

9. The method of claim 8, wherein the one or more operations are selected from the group consisting essentially of:

modifying option settings, read operations, select operations, write operations, commit operations, roll back operations, execute operations, and prepare operations.

10. The method of claim 8, wherein each of the one or more locks has associated with it, a lock number, lock type, lock scope and lock sequence.

11. The method of claim 10 further comprising the step of determining a transaction isolation level associated with the transaction request.

12. The method of claim 11 wherein each lock scope is based on the transaction isolation level.

13. The method of claim 12, wherein each lock scope is based on the database subunit.

14. The method of claim 12 wherein the lock scope is further based on the lock type.

15. A system for processing a transaction request at a database load balancer, said system comprising:

(a) a memory for storing the plurality of images; and

(b) a processor coupled to the memory and for;

(i) receiving the transaction request, where the transaction request is comprised of one or more operations to be performed upon a database;

(ii) analyzing the transaction request to determine the one or more operations and to determine one or more database units associated with the operations;

(iii) analyzing the transaction requests and the one or more database units to determine one or more database subunits associated with the database units that the transaction request will perform one or more operations upon;

(iv) associating one or more database locks with each of the one or more operations;

(v) analyzing one or more of the database locks to determine one or more sequence numbers associated with each of the one or more operations; and

(vi) transmitting the one or more operations with the one or more unique identifiers for each of the database subunits, the database locks and the sequence numbers to one or more database servers accessible to the database load balancer.

16. A system for processing a transaction request at a database load balancer, said system comprising:

(a) a memory for storing the plurality of images; and

(b) a processor coupled to the memory and for;

(i) receiving the transaction request, where the transaction is comprised of one or more operations to be performed upon a database;

(ii) analyzing the transaction request to determine the one or more scripts to be executed through a scripting module;

(iii) determining through the scripting module and associated scripts, the one or more operations, the one or more database units associated with the database record, the one or more database subunits associated with each database unit and the one or more locks with the one or more operations;

(iv) analyzing the one or more database locks to determine one or more sequence numbers associated with each of the one or more operations; and

(v) transmitting the one or more operations with the one or more unique identifiers for each of the database subunits, the associated database locks and the sequence numbers to one or more database servers accessible to the database load balancer.