Getting Startedwith pureQuery

98
Getting Started with pureQuery
• bind you application to use static SQL
• enable literal replacement with parameters during the capture process
• use the Optim Query Tuner to give you advice on improving your queries or
database design.
To replace a poorly performing statement with an optimized one, to use static SQL or both,
refer to Chapter 4.
5.3.1 Optimize your applications by using Optim Query Tuner
DBA’s are frequently more interested in fine tuning SQL statements than developers are.
However, if this task could be made easier, developers could take certain steps to try to
improve application performance during the development stage to avoid expensive or risky
changes during the production stage. With Optim Query Tuner (OQT), you can easily get
advice on writing more efficient SQL or get enough information to ask for new indexes or
statistics from the database administrator.
Note:
For more information on this topic, refer to the Developer Works article at
https://www.ibm.com/developerworks/data/library/techarticle/dm-0906optimdeveloper/ or
the article SQL Tuning on the IBM Data Management Magazine, Issue 2, 2009 pp. 22-25.
Optim Query Tuner is a separate product that integrates with ODS and can be launched
from either of the following places by selecting the Open Query Tuner menu:
• right-click on a SQL statement in the Java Editor
• right-click on a SQL statement in the SQL Outline
• right-click on a SQL statement in the pureQueryXML Editor
To launch OQT, right-click on the SQL statement which took the maximum time to
execute—Figure 14.4—and choose Open Query Tuner from the context menu.