The SQL performance data can be either captured from Java applications that you run on
the workbench or retrieved from an Optim™ Performance
Manager repository.
- To view workbench SQL performance data by running a Java application
- Create a pureQuery Run configuration to run a Java application. You use the SQL Outline view
to evaluate data about the speed at which the associated database
ran the SQL statements that are in the application. You can also compare
current data with previously captured data to determine whether changes
that you made to SQL statements improved their performance.
- To view SQL performance data that is imported from an Optim Performance
Manager repository database
- Create an Optim Performance
Manager profile
to connect to the repository database that contains the performance
data for the SQL statements in your project. You specify a time interval
for the performance data to import. The SQL Outline view
displays the performance data for the SQL statements that are run
dynamically.
You can save sets of performance data. After you find out which
SQL statements are not performing well, you can view their access
plans in Visual Explain. You can also tune them with Optim Query
Tuner.
The SQL Outline view can display the following
types of SQL performance data:
- Workbench SQL performance data
- Performance data that is captured when a Java application runs
SQL statements in the workbench. The data can be captured by pureQuery
Runtime when an SQL statement runs or can be from previously saved
locally-captured performance data.
- Performance manager data
- Performance data that is retrieved from an Optim Performance
Manager repository.
When
you import the Optim Performance
Manager data,
performance data is only visible for SQL statements that are listed
in the SQL Outline view. If the imported data is related to SQL statements
that are not listed in the SQL Outline view, that data is not displayed.
In the
SQL Outline view, you can view only
one type of performance data at a time. In the view, the workbench
performance data is displayed slightly differently than the performance
manager data.
- In the Database page
- If workbench SQL performance data is displayed, data is displayed
on the row that lists the SQL statement and on the row that lists
the SQL statement with program source code line number.
If Optim Performance
Manager performance data
is displayed, the data is displayed on the row that lists the SQL
statement without a line number. The imported data does not contain
the information to match the performance data to a SQL statement at
specific a location in the file. The rows with the line numbers are
grouped with the statement to show locations of the SQL statement
in the source code. If the SQL statement is listed more than once,
the same performance information is displayed for each occurrence
of the statement.
- In the Java page
- If workbench SQL performance data is displayed, the performance
data is displayed on the row that lists a specific SQL statement and
source code line number for a Java file.
If
the Optim Performance
Manager performance
data is displayed, the performance data is displayed for the SQL statement
in the Java file without a line
number. The imported data does not contain the information to match
the performance data to a SQL statement at specific a location in
the file. The rows with the line numbers are grouped with the statement
to show the locations of the SQL statement in the file. If an SQL
statement appears in more than one Java file,
the same performance information is displayed for each occurrence
of the statement.