SQL tuning base

• US 8,983,934 B2
• Filed: 09/07/2004
• Issued: 03/17/2015
• Est. Priority Date: 09/06/2003
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Ramacher, Mark, Bodagala, Sreenath, Dageville, Benoit, Tsukerman, Alex, Vivian, Stephen J., Ziauddin, Mohamed
• Primary Examiner(s): WILSON, KIMBERLY LOVEL
• Application Number:
  US10/936,468
• Publication Number:
  US 20050097091A1
• Time in Patent Office: 3,843 Days
• Field of Search: 707 1- 10, 707/100.S, 707/200.S
• US Class Current: 707/721
• CPC Class Codes: G06F 16/217 Database tuning G06F16/2282 takes precedence; database performance monitoring G06F11/3409
• CPC Class Codes: G06F 16/24549 Run-time optimisation
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

A computer readable medium storing a database query language statement tuning base in a tuning base memory location is disclosed. The tuning base includes tuning information for one or more query language statements. The tuning information for each statement includes one or more tuning actions for the statement, and a signature to allow an optimizer to identify the one or more tuning actions for the statement.

Claims

1. An article of manufacture comprising a volatile or non-volatile computer readable storage medium storing a system for tuning database query language statements, comprising:

a tuning base containing tuning information for a database query language statement, the tuning information comprising;

trace information for the database query language statement, wherein

the trace information comprises statistics of a database object for the database query language statement, wherein the statistics in the trace information are adjusted to tune execution of the database query language statement when the database query language statement is compiled or executed; and

a signature which is generated during compilation of the database query language statement and is used to identify the trace information for the database query language statement; and

a query optimizer that tunes the database query language statement at least by retrieving at least the tuning information from the tuning base during compilation of the database query language statement, based at least in part the signature for the database query language statement, wherein

the query optimizer tunes the database query language statement at least by modifying a compiled database query statement of the database query language statement to include at least a part of the tuning information for the execution of the compiled database query statement with an execution plan, and

the query optimizer adjusts the statistics in the trace information to tune the database query language statement, by using one or more statistics adjustment hints.

2. The article of claim 1, the tuning information further comprising:

tracing information collected during one or more previous executions of the statement.

3. The article of claim 1, the tuning information further comprising:

an outline to persistently represent a stored execution plan of the statement.

4. The article of claim 1, the tuning information further comprising:

a profile to persistently represent tuning hints to influence a generation of the execution plan of the statement.

5. The article of claim 1, the computer readable storage medium further comprising:

one or more SQL statements stored in a second memory location that is independent of a memory location storing the tuning base.

6. The article of claim 1, wherein the signature for the statement is based on a normalized text of the statement.

7. The article of claim 1, wherein the database query language statement is a SQL statement.

8. A computer implemented method for retrieving tuning information for a database query language statement, the method comprising:

receiving a signature, the signature being generated based on a database query language statement during compilation of the database query language statement, wherein

the signature allows an optimizer at a database server to identify trace information for the database query language statement for retrieving the tuning information during the compilation of the database query language statement, and

the trace information comprises statistics of a database object for the database query language statement;

determining, by using a processor, whether trace information for the database query language statement is available based at least in part upon the signature;

tuning the database query language statement at least by retrieving the tuning information based at least in part upon the signature for the database query language statement from a tuning base, and further by modifying a compiled database query statement of the database query language statement to include at least a part of the tuning information for execution of the compiled database query statement with an execution plan; and

adjusting the statistics in the trace information, which is used to further tune the database query language statement, by using one or more statistics adjustment hints.

9. The method of claim 8, the tuning information further comprising:

tracing information collected during one or more previous executions of the statement.

10. The method of claim 8, the tuning information further comprising:

an outline to persistently represent a stored execution plan of the statement.

11. The method of claim 8, the tuning information further comprising:

a profile to persistently represent tuning hints to influence a generation of the execution plan of the statement.

12. The method of claim 8, wherein one or more SQL statements are stored in a memory location that is independent of a memory location storing the tuning base.

13. The method of claim 8, wherein the signature for the statement is based on a normalized text of the statement.

14. The method of claim 8, wherein the statement is an SQL statement.

15. The method of claim 8, wherein determining whether trace information for the database query language statement is available comprises:

mapping the signature to a lookup table.

16. The computer implemented method of claim 8, wherein the act of determining whether the trace information is available is performed by using at least a negative identification case.

17. The computer implemented method of claim 8, wherein at least a part of the tuning information is copied into the database query language statement.

18. The computer implemented method of claim 8, wherein the tuning information comprises a profile which provides one or more tuning functions for tuning the database query statement.

19. The computer implemented method of claim 8, wherein the tuning information comprises an outline which provides execution plan editing capability.

20. A system for retrieving tuning information for a database query language statement, the system comprising:

a hardware processor for performing;

receiving a signature, the signature being generated based on a database query language statement during compilation of the database query language statement, wherein

the signature allows an optimizer at a database server to identify trace information for the database query language statement for retrieving the tuning information during the compilation of the database query language statement, and

the trace information comprises statistics of a database object for the database query language statement;

determining, by using a processor, whether trace information for the database query language statement is available based at least in part upon the signature;

tuning the database query language statement at least by retrieving the tuning information based at least in part upon the signature for the database query language statement from a tuning base, and further by modifying a compiled database query statement of the database query language statement to include at least a part of the tuning information for execution of the compiled database query statement with an execution plan; and

adjusting the statistics in the trace information, which is used to further tune the database query language statement, by using one or more statistics adjustment hints.

21. The system of claim 20, the tuning information further comprising:

tracing information collected during one or more previous executions of the statement.

22. The system of claim 20, the tuning information further comprising:

an outline to persistently represent a stored execution plan of the statement.

23. The system of claim 20, the tuning information further comprising:

a profile to persistently represent tuning hints to influence a generation of the execution plan of the statement.

24. The system of claim 20, wherein one or more SQL statements are stored in a memory location that is independent of a memory location of the tuning base.

25. The system of claim 20, wherein the signature for the statement is based on a normalized text of the statement.

26. The system of claim 20, wherein the statement is an SQL statement.

27. The system of claim 20, wherein the tuning information further comprising:

means for mapping the signature to a lookup table.