A Query Tuner project is the largest structural
unit for
single-query tuning and workload tuning in the Project Explorer. You
can start tuning without first creating a Query Tuner project. However,
if you want to save your work and return to it later, you must save
it in a Query Tuner project.
A Query Tuner
project contains the artifacts for query-tuning
and workload-tuning activities:
- Query group
- A
query group is a folder that contains one or more SQL statements
and the analysis results for the SQL statements. You can organize
multiple SQL statements within a single query group for different
versions of the same query. To add a query to the query group, right-click
a query group and select Create Query.
Tip: No relationship is enforced between the different SQL statements
in a query group, and the group can contain the text of separate SQL
statements. However, a good practice is to use one query group to
hold the different versions of a query as you modify the query during
the tuning process. Saving different versions of a query is useful
if you need to backtrack.
- Query
- Each query object in a Query Tuner project is a resource unit
that contains the text of a query and some information about the context
of the query. Each query can have multiple analysis results associated
with it. You can use the different analysis results to track the performance
improvements over time, and to keep a record of your tuning activities.
When you double-click a query object in a Query Tuner project, the
workflow assistant for query tuning opens, so that you can run the
advisors and analysis tools.
- Workload group
- A workload group is a folder that contains multiple workload objects.
Unlike a query group, the workload group does not contain the analysis
results for the workloads. The analysis results of a workload are
saved on the DB2® for z/OS® subsystems.
You can right-click a workload group and select Tune Workload to
create a workload or attach an existing workload on the subsystem
for the workload group.
- Workload
- Each
workload object in a Query Tuner project is a resource unit
that contains the information about the workload on the subsystem,
including the connection alias and the workload name. The statements
of a workload and the analysis results are not contained in the workload
object; they are created and saved on the subsystem. When you double-click
a workload object in a Query Tuner project, the workflow assistant
for Query Tuner opens, so that you can run the advisors and the analysis
tools.
- Analysis result
- Each analysis
result object in a Query Tuner project is a resource
unit to contain the various artifacts that you use for analyzing and
tuning SQL statements, including the formatted and annotated query,
the access plan graph, and the summary of advisor recommendations.
When you double-click an analysis result object in a Query Tuner project,
the workflow assistant for query tuning opens, so that you can review
the recommendations.
- SQL script
- Each
SQL script is a file that contains the text of the script.
You can create an SQL script in a Query Tuner project by right-clicking
the project and selecting . When you double-click
a script, the SQL editor opens. You can enter a script in the editor
as a new query for tuning, or you can verify whether the script can
be executed.