Getting Startedwith pureQuery

94
Getting Started with pureQuery
From the SQL Outline or through the Java Editor, take advantage of ODS integration with
Optim Query Tuner (OQT) to get expert advise on improving your queries and database
design through its easy-to-use advisors.
5.2 Identify the time and frequency of execution and cost of a
statement
Though the SQL Outline, you can drill down and see the performance metrics for any SQL
statement that was executed providing you with information to quickly and easily identify
the statements that would need to be optimized.
Note:
You can view performance metrics for applications that use the pureQuery API—methodstyle
or inline-style, as well as JDBC, Hibernate or JPA applications.
The performance metrics provide you information such as:
• Number of times the SQL ran
• Total execution time—adds the time for each run of the same SQL
• Longest time the SQL took to run
• Average of time that the SQL took to run
• Minimum time the SQL took to run
5.2.1 Gathering and viewing performance metrics
To view the performance metrics when executing your Java application, you must run your
application under the PureQuery configuration and not as a regular Java Application.