Written by Rene Woody
This blog is a
continuation of a series about the Batch Optimizer in Quest SQL Optimizer
for Oracle. The Batch Optimizer process is fully automated with the default settings in the Batch Optimizer options. If you would like, you can have any one of the three steps (searching for SQL, optimizing SQL, and testing SQL alternatives) pause and wait for you to continue the process. The option settings for the Batch Optimizer in Quest SQL Optimizer
for Oracle enable you to control the types of SQL statements that are optimized and which of the SQL alternatives are executed.
This blog covers the options settings for the first two steps in the Batch Optimizer process, the searching for SQL statements and the optimization of the SQL statements. The other Batch Optimizer option settings will be covered in upcoming blogs.
Searching Options
The Batch Optimizer automatically starts searching for SQL statements in a job as soon as the job is added to the batch queue. By clearing the Automatically start extracting SQL when job is added setting, you can have the job wait until you manually start.
The jobs are searched using the settings in the SQL Scanner settings. The specific settings for the SQL Scanner will be covered in another topic.
Optimizing Options
When the searching process is finished, the optimization process automatically starts to optimize the SQL statements one-by-one. The SQL to automatically optimize setting determines the specific SQL statements which are optimized using the SQL classifications (Simple, Complex, and Problematic). For example, with the default setting of Problematic, only those SQL statements that are classified as Problematic during the searching process will automatically be optimized. If none of the SQL classifications are selected, then you must manually select each SQL statement to be optimized.
The SQL statements are optimized using the Optimizer settings. The specific settings for the optimization will be covered in another topic.