Getting Startedwith pureQuery

112
Getting Started with pureQuery
Run: Dynamic mode, captured-only mode
pureQuery Properties:
pdq.executionMode=DYNAMIC
pdq.capturedOnly=TRUE
Database
Configured
pureQueryXml
File
pureQuery
Yes
Execute
JDBC
Application
Run
SQL
Statement
Is the
SQL in the
pureQueryXml
file?
No
Exception
Dynamic
Statement
Cache
Figure 6.8- You can direct pureQuery to execute only SQL statements that
are in the capture file. You can specify that it execute all statements
dynamically.
6.3 JDBC driver requirements for using Client Optimizer functionality
In order to use the Client Optimizer, make sure that pureQuery supports the JDBC driver
that you are using, and that its version meets the requirements of the pureQuery release.
If you are using the IBM Data Server Driver for JDBC and SQLJ as your JDBC driver, all
that you need to do is have the pureQuery JAR files pdq.jar and pdqmgmt.jar in the
classpath of the JDBC driver when the application creates a javax.sql.DataSource or
java.sql.Connection object.
If you are using an Oracle database, your application must use a
javax.sql.DataSource object to create Connection objects. Your DataSource object
will need to be an instance of one of several DataSource classes that pureQuery
provides. Each of these classes wraps or extends a DataSource object that an Oracle
JDBC driver provides. Refer to the IBM Optim pureQuery Runtime documentation for
information on how to use the Client Optimizer for Oracle databases.
6.4 pureQuery properties
pureQuery has a number of properties, called pureQuery properties. Several of these
properties control the behavior of the Client Optimizer. The names of all of the pureQuery
properties start with “pdq.”. For example, there is a property named pdq.captureMode.