SQL Optimizer for DB2 LUW 5.0 - User Guide

Create Benchmark Factory Import File

All the SQL statements can be saved in a text file from the Job Manager, the Scanned SQL Viewer, the SQL Repository, and the SQL Optimizer windows. These SQL statements can then be imported into Benchmark Factory program (version 4.6 or later).

To create the text file to import into Benchmark Factory

1. Right-click and select Create Benchmark Factory Import File.

2. Select the specific SQL statements that you want to save. Click OK.

3. Enter the filename and select the file location. Click Save.

Job Manager Functions

Below is a list of available functions within the Job Manager window.

Scanned SQL Viewer

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)

SQL Formatter

Database Explorer

SQL Scanner

SQL Inspector

SQL Repository

Index Impact Analyzer

Index Usage Analyzer

About Scanned SQL Viewer

The Scanned SQL Viewer window enables the viewing and analysis of the SQL statement scanned. It displays the formatted scanned SQL statement, access plan, temp table (if applicable), and information about the SQL statement.

• Formatted scanned SQL statement

• Access plan

• SQL Information

• SQL statement type classification: Problematic, Complex, Simple, or Invalid.

• Database error message if SQL is classified as Invalid,

• Information about any SQL conversion the SQL Scanner applied to the SQL statement in order for it to generate a access plan

• Line and column where the SQL statement was found in the source (for database object and source code files only)

• SQL statement used to create and populate any temporary tables the SQL Scanner created

• Checked SQL Information (if the SQL has been marked as checked)

• Date time of when the SQL statement was checked

• Name of who checked the SQL

• Status

• Checked description are displayed