SYSTEM AND METHOD FOR PERFORMING COMMUTATIVE OPERATIONS IN DATA ACCESS SYSTEMS

• US 20080091683A1
• Filed: 12/07/2007
• Published: 04/17/2008
• Est. Priority Date: 05/23/2002
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Messigner, Adam
• Granted Patent: US 7,895,153 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

An embodiment of the invention allows a software developer or administrator to use their knowledge and/or development of a particular application, to optimize the performance of data access and updates to the database. In order to do this, an embodiment of the invention makes use of the developers knowledge of particular transaction and transaction operations that can be performed in a commutative manner. The overall effect is to perform the operations in a parallel fashion so that one operation does not block or restrict the processing of a second operation. The result is an increase in database access or performance, without any resulting decrease in database reliability.

Claims

1. A system, comprising:

a server that receives transaction requests to perform database operations to update data within a database; and

one or more configuration file, including

information that identifies to the server specific database operations that are allowed to be performed commutatively; and

information that specifies to the server boundary conditions that constrain commutative execution of database operations to only those database operations whose combined effect on the database is within the boundary conditions.

2. The system of claim 1, wherein the server will perform database operations commutatively if the operations are specified as being allowed to performed commutatively, and the combined effect of the operations on the database is within the boundary conditions.

3. The system of claim 1, wherein server will perform database operations consecutively if the operations are not specified as being allowed to be performed commutatively.

4. The system of claim 1, wherein server will perform database operations consecutively if the combined effect of the operations on the database is not within the boundary conditions.

5. The system of claim 1, wherein if database operations are specified as being allowed to be performed commutatively, but the combined effect of the operations on the database is not currently within the boundary conditions, the server delays performance of the operations until the combined effect of the operations on the database is within the boundary conditions.

6. The system of claim 1, wherein if database operations are specified as being allowed to be performed commutatively, but the combined effect of the operations on the database is not currently within the boundary conditions, the server performs the operations consecutively.

7. The system of claim 1, wherein at least one of an application developer and an administrator can specify the specific database operations that are allowed to be performed commutatively.

8. The system of claim 1, wherein at least one of an application developer and an administrator can specify the boundary conditions.

9. The system of claim 1, wherein at least one of an application developer and an administrator can specify:

the specific database operations that are allowed to be performed commutatively; and

the boundary conditions.

10. The system of claim 1, further comprising:

a means for allowing at least one of an application developer and an administrator to specify the specific database operations that are allowed to be performed commutatively; and

a means for allowing at least one of a software developer and an administrator to specify the boundary conditions.

11. A method, comprising:

storing information that identifies specific database operations that are allowed to be performed commutatively;

storing information that specifies boundary conditions that constrain commutative execution of database operations to only those database operations whose combined effect on a database is within the boundary conditions;

receiving transaction requests including database operations to update data within the database; and

allowing database operations to run commutatively upon the database if the operations are identified as being allowed to be performed commutatively and if the combined effect of the operations on the database is within the specified boundary conditions.

12. The method of claim 11, further comprising performing database operations consecutively if the operations are not specified as being allowed to be performed commutatively.

13. The method of claim 11, further comprising processing database operations consecutively if the combined effect of the operations on the database is not within the boundary conditions.

14. The method of claim 11, wherein if database operations are specified as being allowed to be performed commutatively, but the combined effect of the operations on the database is not currently within the boundary conditions, delaying the processing of the operations until the combined effect of the operations on the database is within the boundary conditions.

15. The method of claim 11, wherein if requested database operations are specified as being allowed to be performed commutatively, but the combined effect of the operations on the database is not currently within the boundary conditions, processing of the database operations consecutively.

16. The method of claim 11, further comprising:

allowing at least one of an application developer and an administrator to specify the specific database operations that are allowed to be performed commutatively.

17. The method of claim 11, further comprising:

allowing at least one of an application developer and an administrator to specify the boundary conditions.

18. The system of claim 11, further comprising:

allowing at least one of an application developer and an administrator to specify the specific database operations that are allowed to be performed commutatively; and

allowing at least one of an application developer and an administrator to specify the boundary conditions.

19. A system, comprising:

a database that stores data;

a server that receives transaction requests to perform database operations to update the data within the database;

configuration information that identifies to the server specific database operations that are allowed to be performed commutatively; and

configuration information that specifies to the server boundary conditions that constrain commutative execution of database operations to only those database operations whose combined effect on the database is within the boundary conditions.

20. The system of claim 19, wherein the server is configured to:

perform database operations commutatively if the operations are specified as being allowed to performed commutatively, and the combined effect of the operations on the database is currently within the boundary conditions; and

perform database operations consecutively if the operations are not specified as being allowed to be performed commutatively.

21. The system of claim 20, wherein if database operations are specified as being allowed to be performed commutatively, but the combined effect of the operations on the database is not currently within the boundary conditions, the server delays performance of the operations until the combined effect of the operations on the database is within the boundary conditions.

22. The system of claim 20, wherein if database operations are specified as being allowed to be performed commutatively, but the combined effect of the operations on the database is not currently within the boundary conditions, the server performs the operations consecutively.