Getting Startedwith pureQuery

Chapter 6 – The Client Optimizer: pureQuery for Existing Applications 101
ascending or descending order to view which statements take the most time to execute, for
example.
Once you have identified which statements take the longest to execute or any other
statement that you believe needs optimizing you can easily replace a poorly performing
statement with an optimized one using the pureQueryXML Editor. Developers can take
certain steps to improve application performance during the development stage to avoid
expensive or risky changes during the production stage.
With Optim Query Tuner, which easily integrates with ODS, 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. Save the performance metrics, replace your SQL with
better performing one and re-run your application and compare the new results with the old
ones.
5.6 Review Questions
1. Which of the following information can be seen in the SQL Outline pertaining to the
execution a SQL Statement?
A. Number of Times Run
B. Total Time
C. Max Time
D. all of the above
2. Performance metrics for the execution of SQL statements can be gathered for which of
the following types of applications?
A. JPA
B. JDBC
C. Hibernate
D. all of the above
3. Under which Configuration within ODS must a user run their application in order to
gather the performance metrics?
A. Java Application
B. PureQuery
C. Eclipse Application
D. Java Applet
4. In which of the following ways can you optimize your application for performance
through ODS?
A. replace poorly performing SQL through the pureQueryXML Editor