As you add SQL statements to the job on the Overview tab of the tuner, tuning-supported DML statements are parsed from the statements and added to the Overview tab in preparation for the tuning function execution.
Each tuning source statement is listed by Name, Schema, Text, Tables and Views. Additionally, each statement will have Time and Analysis values that approximate how efficiently they execute on the specified data source.
In the Generated Cases area of the Overview tab of a tuning job, the Cost and Execution Statistics columns let you compare the relative efficiency of SQL statements or statement cases. While the explain plan Cost for a statement or case is calculated when you add SQL to a tuning job, the Elapsed Time and Execution Statistics (and Other Execution Statistics columns, if available) columns are not populated until you execute that statement or case.
If the Tuning Status Indicator indicates that a statement or case is ready to execute, you can execute one or more statements on the Overview tab. Alternatively, the Tuning Status Indicator may show that you have to correct the SQL or set bind variables before you can execute.
Once the tuning job has run, the Overview tab provides a series of cases, per statement, that you can select and modify based on your results.
In some cases, automatic case generation might be disabled (via the Preferences panel). If this is true, or if you have otherwise modified the Generated Cases table and can no longer generate a specific case, you can instead explicitly generate a case for specific statements.
To execute a tuning job
To explicitly generate a case for a specific statement
To view the generated cases for a specific statement
| | | | | | | |