SQL structure analyzer

• US 7,634,456 B2
• Filed: 09/07/2004
• Issued: 12/15/2009
• Est. Priority Date: 09/06/2003
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Dias, Karl, Zait, Mohamed, Yagoub, Khaled, Dageville, Benoit, Ziauddin, Mohamed
• Primary Examiner(s): Vo; Tim T.
• Assistant Examiner(s): Morrison; Jay A
• Application Number:
  US10/936,426
• Publication Number:
  US 20050120001A1
• Time in Patent Office: 1,925 Days
• Field of Search: 707/2
• US Class Current: 1/1
• 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 method to addresses structural performance problems of a database query language statement is provided. The method includes receiving a database query language statement at an optimizer, evaluating choices in a search space to generate an execution plan for the statement, and producing annotations to record one or more reasons for selecting each choice while generating the execution plan.

Claims

1. A method comprising:

receiving a database query language statement at an optimizer;

evaluating one or more choices in a search space to identify or generate an optimal execution plan for the database query language statement;

generating an annotated execution plan from the optimal execution plan by producing and storing one or more annotations in the annotated execution plan to explain one or more reasons for the optimizer selecting a choice over an alternative choice during the act of evaluating the one or more choices, wherein

the annotated execution plan is examined for identifying or generating a recommendation for one or more schema changes and the possible statement modification to rewrite the database query language statement; and

displaying the recommendation on a display apparatus or storing the result in a tangible computer usable medium or a storage device.

2. The method of claim 1, wherein the one or more annotations for a selected choice comprises:

one or more semantically different alternatives to the selected choice;

reasons for not performing one or more rewrites of the database query language statement; and

information to be displayed to a developer of the database query language statement.

3. The method of claim 2, further comprising:

associating the one or more annotations for each selected choice to a corresponding operator of the database query language statement.

4. The method of claim 3, further comprising:

identifying operators of the database query language statement having a cost above a threshold cost;

for each costly operator, examining the one or more annotations associated with the identified operator; and

generating a structural recommendation about the costly operator to improve the database query language statement.

5. The method of claim 4, wherein generating the structural recommendation comprising:

retrieving an alternative operator from the one or more annotations;

comparing a cost of the alternative operator with a cost of the costly operator; and

mapping the recommendation to use the alternative operator to the costly operator in the database query language statement.

6. The method of claim 5, further comprising:

rewriting the database query language statement with the alternative operator; and

generating an execution plan for the database query language statement with the alternative operator.

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

8. An apparatus comprising:

means for receiving a database query language statement at an optimizer;

means for evaluating one or more choices in a search space to identify or generate an optimal execution plan for the database query language statement;

means for generating an annotated execution plan from the optimal execution plan by producing and storing one or more annotations in the annotated execution plan to explain one or more reasons for the optimizer selecting a choice over an alternative choice during the act of evaluating the one or more choices, wherein

the annotated execution plan is examined for identifying or generating a recommendation for one or more schema changes and the possible statement modification to rewrite the database query language statement; and

a display apparatus configured for displaying the recommendation or a tangible computer usable medium or a storage device configured for storing the result.

9. The apparatus of claim 8, wherein said means for producing the one or more annotations comprises:

means for generating one or more semantically different alternatives to the selected choice that each, if used in the database query language statement, produce the same result;

means for generating reasons for not performing one or more rewrites of the database query language statement; and

means for generating information to be displayed to a developer of the database query language statement.

10. The apparatus of claim 9, further comprising:

means for associating the one or more annotations for each selected choice to a corresponding operator of the database query language statement.

11. The apparatus of claim 10, further comprising:

means for identifying operators of the database query language statement having a cost above a threshold cost;

means for examining the one or more annotations associated with each identified operator; and

means for generating a structural recommendation about the costly operator to improve the database query language statement.

12. The apparatus of claim 11, wherein said means for generating the structural recommendation comprising:

means for retrieving an alternative operator from the one or more annotations;

means for comparing a cost of the alternative operator with a cost of the costly operator; and

means for mapping the recommendation to use the alternative operator to the costly operator in the database query language statement.

13. The apparatus of claim 12, further comprising:

means for rewriting the database query language statement with the alternative operator; and

means for generating an execution plan for the database query language statement with the alternative operator.

14. The apparatus of claim 8, wherein the database query language statement is a SQL statement

15. A volatile or non-volatile computer readable medium storing a computer program of instructions which, when executed by a processing system, cause the system to perform a method comprising:

receiving an database query language statement at an optimizer;

evaluating one or more choices in a search space to identify or generate an optimal execution plan for the database query language statement;

generating an annotated execution plan from the optimal execution plan by producing one or more annotations to explain one or more reasons for the optimizer selecting a choice over an alternative choice during the act of evaluating the one or more choices, wherein

the annotated execution plan is examined for identifying or generating a recommendation for one or more schema changes and the possible statement modification to rewrite the database query language statement.

16. The medium of claim 15, wherein the one or more annotations for each selected choice comprising:

one or more semantically different alternatives to the selected choice that each, if used in the database query language statement, produce the same result;

reasons for not performing one or more rewrites of the database query language statement; and

information to be displayed to a developer of the database query language statement.

17. The medium of claim 16, wherein the executed instructions further perform the method comprising:

associating the one or more annotations for each selected choice to a corresponding operator of the database query language statement.

18. The medium of claim 17, wherein the executed instructions further perform the method comprising:

identifying operators of the database query language statement having a cost above a threshold cost;

for each costly operator, examining the one or more annotations associated with the identified operator; and

generating a structural recommendation about the costly operator to improve the database query language statement.

19. The medium of claim 17, wherein the executed instructions further perform generating the structural recommendation comprising:

retrieving an alternative operator from the one or more annotations;

comparing a cost of the alternative operator with a cost of the costly operator; and

mapping the recommendation to use the alternative operator to the costly operator in the database query language statement.

20. The medium of claim 19, wherein the executed instructions further perform the method comprising:

rewriting the database query language statement with the alternative operator; and

generating an execution plan for the database query language statement with the alternative operator.

21. The medium of claim 15, wherein the database query language statement is SQL statement.

22. A method comprising:

receiving a database query language statement at an optimizer;

evaluating one or more choices for operators of the database query language statement to generate an optimal execution plan for the database query language statement;

selecting a choice for each operator;

generating an annotated execution plan from the optimal execution plan by producing and storing one or more annotations in the annotated execution plan to explain one or more reasons for one or more rejected choices that have been rejected by the optimizer for an operator;

generating one or more recommendations for one or more schema changes and for changing one of the operators to rewrite the database query language statement based on the annotations; and

displaying the one or more recommendations on a display apparatus or storing the result in a tangible computer usable medium or a storage device.

23. The method of claim 22, wherein generating recommendations comprises:

identifying a costly operator of the database query language statement;

identifying a rule from the one or more annotations for the costly operator; and

identifying a less costly operator based on the rule.

24. The method of claim 23, further comprising:

recommending that a user rewrite the database query language statement by replacing the costly operator with the less costly operator.

25. A method comprising:

receiving a database query language statement at a query optimizer;

evaluating one or more choices in a search space at the query optimizer to generate an optimal execution plan for the database query language statement;

generating an annotated execution plan from the optimal execution plan by producing one or more annotations in the annotated execution plan, at the query optimizer, to explain one or more reasons for the query optimizer selecting or rejecting a choice over an alternative choice during the act of evaluating the one or more choices, wherein

the annotated execution plan is examined for generating a recommendation for one or more schema changes and the possible statement modification to rewrite the database query language statement;

examining, at the query optimizer, the one or more annotations; and

displaying the recommendation on a display apparatus or storing the result in a tangible computer usable medium or a storage device.

26. The method of claim 25, further comprising:

generating, at the query optimizer, appropriate recommendations to improve performance based on rules in a knowledge base.

27. The method of claim 26, wherein each recommendation includes a recommendation to make database schema changes.

28. The method of claim 26, wherein each recommendation is associated with a rationale and informative messages for user understandability.

29. The method of claim 26, wherein each recommendation is mapped to a corresponding SQL operator in the database query language statement.

30. The method of claim 26, wherein the method further comprising:

producing rewritten statement text for a user.

31. The method of claim 26, wherein the rules in the knowledge base can be customized by a user by adding additional rules or removing existing rules.