The Batch Run Details window displays a summary of the run time information for all SQL and index-set alternatives executed. The Batch Run Details window will appear after the batch run process is completed unless the Show details on next batch run checkbox in the Batch Run Details window is unchecked.
To review the Batch Run Details window
After the Batch Run is complete and the SQL Optimizer window is active, select View | Show Batch Run Details.
Quest SQL Optimizer for IBM® DB2® LUW maximizes SQL performance by automating the manual, time-intensive and uncertain process of ensuring that SQL statements are performing as fast as possible. SQL Optimizer analyzes, rewrites, and evaluates SQL statements within multiple database objects, files. With SQL Optimizer, you can analyze and optimize all your problem SQL from multiple sources. SQL Optimizer also provides you a complete index optimization and plan change analysis solution, from index recommendations to simulated index impact analysis, through comparison of multiple SQL access plans.
SQL Optimizer provides you with the following main modules.
SQL Optimizer (including SQL Rewrite and Generate Indexes functions)
The Selected SQL/Index Set tab of the Batch Run Criteria window is used to select the SQL and index-set alternatives you want to execute. By default, all alternatives are initially selected.
Tip: To save all settings on the Batch Run Criteria dialog for subsequent batch runs, select Save setting for the next batch run.
To select or deselect an alternative
Double-click an SQL or index-set alternative.
To select or deselect all alternatives
Right-click and select Select All or Unselect All.
To select alternatives according to the cost values
Click SQL/Index Sets selection filter 
Review the DB2 LUW cost retrieved from the virtual plans.
Check the Exclude SQL/Index Set with DB2 LUW cost greater than checkbox and enter a DB2 LUW cost.
Note: The original SQL statement can be de-selected only if the Original SQL option is not selected in the SQL Termination tab of the Batch Run Criteria window and the Always run Original SQL first option is not selected.
The alternatives are ranked by DB2 LUW Cost by default, with the exception of the original SQL, which is placed at the top.
To change the execution order using the DB2 LUW cost
Click either the DB2 LUW or the SQL/Index Set column heading to reorder the alternatives for execution.
Note: High DB2 LUW Cost does not necessarily mean slower performance. If possible, it is recommended that all alternatives be tested.
To change the execution order for individual alternatives
Select the SQL or index-alternative; then click Move Up 
The original SQL statement can always be run first even if it does not have the lowest DB2 LUW cost.
To always run the original SQL statement first
Select the Always run Original SQL first checkbox.
This checkbox is disabled if Original SQL is selected as a termination criterion on the SQL Termination tab or the Batch Termination tab since the run time from the original SQL is going to be used to terminate the alternatives or to terminate the Batch Run itself. In this case, you must run the original SQL statement first to obtain the termination time.
The SQL Termination tab of the Batch Run Criteria window is used to set the SQL termination criteria for each SQL and index-set alternative for which you are retrieving run times. If the current run time for a particular alternative exceeds the termination time, then the execution of the alternative terminates automatically. This will save time during testing.
Tip: To save all settings on the Batch Run Criteria dialog for subsequent batch runs, select Save setting for the next batch run.
The percentage-delay calculation adds additional time to the termination time. It is used to account for the time it takes an alternative to travel from the local computer to the database server over the network.
|
Option |
Description |
|
Percentage delay (%) |
The value entered into this box is used as a percentage to calculate the additional time that is added to the termination time. For example, if the termination time is 10 minutes and the percentage delay is 5%, then all alternatives executed are terminated if the run time exceeds 10.5 minutes. (10+ (10 * 5%)) |
|
Minimum delay time (secs) (Default = 5, Range 1 – 99) |
This is minimum number of seconds that is added to the termination time. It is necessary to factor into the overall termination time the time needed for the alternative be sent to the database server from the local computer before it starts to run. This number is only used if the percentage-delay calculation is lower than this value. |
|
Maximum delay time (mins) (Default = 60, Range 1 – 9999) |
This is the maximum number of minutes that can be added to the termination time. This number is only used if the percentage-delay calculation is higher than this value. |
|
Option |
Description |
|
Run without termination |
Executes all the alternatives until they are completed. |
