View the Batch Run Criteria Window (Selected Index Set)
The Selected Index Set tab of the Batch Run Criteria window is used to select or deselect which Index Sets are applied before retrieving the run time for the original SQL statement. Selected Index Sets are prefixed with a blue checkmark . All Index Sets are selected by default.
To select or deselect one Index Set
Double-click the Index Set row.
To select or deselect all Index Sets
Right-click and select Select All or Unselect All.
To select Index Sets according to the cost values using the selection filter
Select the Apply Index selection filter checkbox.
Click Index selection filter .
Review the DB2 LUW cost retrieved from the virtual plans.
Check the Exclude SQL with DB2 LUW cost greater than checkbox and enter a DB2 LUW cost.
Note: The Used Index can be de-selected only if the Used Index option is not selected in the SQL Termination tab of the Batch Run Criteria window and the Always run Used Index first option is not selected.
The Index Sets are ranked by DB2 LUW Cost by default, with the exception for the Used Index which is placed at the top.
To change the execution order using the DB2 LUW cost
Click the column heading for either the DB2 LUW column or the SQL column to use the execution based on the corresponding column.
Note: High DB2 LUW cost does not necessary mean slower performance. If possible, it is recommended that all alternative indexes be tested.
To change the execution order for individual Index Sets
Click the row and then click Move Up or Move Down .
The Used Index can always be run first even if it is not the index option that has the lowest DB2 LUW cost.
To always run Used Index first
Select the Always run Used Index first checkbox.
This checkbox is dimmed if Used Index is selected as a termination criterion on the SQL Termination tab or the Batch Termination tab since the run time from the existing indexes is going to be used to terminate the SQL statement using the other index options or to termination the Batch Run itself. In this case, you must run the SQL statement with the currently used indexes first to obtain the termination time.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center