SQL Optimizer for SAP ASE 3.9.1

In the SQL Scanner window, initially all SQL statements in the selected Job are shown. Customization of the view allows the displaying of: All, Simple, Problematic, Complex, and/or Invalid SQL statements. In addition, you can view the Checked and/or Unchecked SQL statements. The title bar of the SQL Scanner window displays the chosen criteria. One or more types of SQL statements can be viewed by selecting or de-selecting the menu items.:

To display SQL statements

Select View | option.

Generate Report for Scanned SQL

SQL Scanner > Generate Report for Scanned SQL

View Scanner SQL Report Criteria Window

You can generate a report with the SQL statements in the SQL Scanner window. The contents of the report depend on the components you select.

Select Report | Scanned SQL to open the Scanned SQL Report Criteria window.
Select the components for the report.
Select All SQL or Select SQL and enter the specific SQL statement numbers.
Click OK to generate the report. The information in the report can be saved and printed.

Note: A few minutes may be needed to generate a long report.

Save Abstract Plan

SQL Scanner > Save Abstract Plan

To save the abstract plan from the SQL Scanner to the database

Click $image\B_SaveAbstractPlan.gif$ .
In the Save to group drop-down field, select the group where you want to store your abstract plan.
Click Save.

When the Abstract Plan is saved, it is only saved for the user that you are logged on as. In order for another user to use this abstract plan, you must export/import the plan to another user.

At the prompt "Plan has been created successfully. The id is nnnnnnnnnn". Click OK. The abstract plan is saved in Adaptive Server.

Notes:

Adaptive Server saves the abstract plan in the sysqueryplans system table. When a query is executed, Adaptive Server looks in the sysqueryplans table for a stored SQL text that matches the query. If a match is found, the saved abstract plan is used to execute the query.

Saving the abstract plan onto the database means that when the same SQL statement is executed, the query plan is based on the abstract plan.
When saving the abstract plan, Adaptive Server automatically trims the white-spaces from the SQL text replacing it with one space. You need to make sure the SQL statement you execute in your application is the same as the original SQL text that you saved with the abstract plan. If the SQL text does not match, then the abstract plan will not be used.

Here are some examples you need to be aware of:

Spaces in between functions

where substring ( EMP_NAME, 1, 5 ) = 'SMITH'

This is not the same as

where substring(EMP_NAME,1,5) = 'SMITH'

Spaces in between database, scheme and object name

from sqlexp . sqlexp . EMPLOYEE

This is not the same as

from sqlexp.sqlexp.EMPLOYEE

Parameter replacement

where EMP_ID = @var_a

This is not the same as

if @var_a = 56

where EMP_ID = 56

Comments

where EMP_ID =123 /* comment */

This is not the same as

where EMP_ID = 123

Create Benchmark Factory Import File

SQL Repository > Create Benchmark Factory Import File

All the SQL statements can be saved in a text file from the SQL Scanner, the SQL Repository, the SQL Inspector, and the SQL Optimizer windows. These SQL statements can then be imported into Benchmark Factory 4.6 or later.

To create a file to import into Benchmark Factory

Right-click and select Create Benchmark Factory Import File.
Select the specific SQL statements that you want to save.
Enter the filename and select the file location.

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem

SQL Optimizer for SAP ASE 3.9.1 - User Guide

View a Particular SQL Type

Generate Report for Scanned SQL

Save Abstract Plan

Create Benchmark Factory Import File