Guidelines and recommendations for pureQuery client optimization
General guidelines, best practices, and usage recommendations
are provided for using applications that are enabled with pureQuery
client optimization.
The Java environment for pureQuery client optimization
Java environment
guidelines and recommendations for pureQuery client optimization include
considerations for connection type, classpath settings, and DB2® for z/OS® data sources. In addition tools are available
for verifying configuration and property resolution.
Recommendations for capturing SQL statements with pureQuery client optimization
For best results, perform the capture SQL data with pureQuery
client optimization during the end of the development phase or during
the test phase. Set the pureQuery Runtime properties appropriately
to control the capture SQL data that is captured, and shut down the
application after capturing SQL data.
Recommendations for configuring and binding pureQueryXML files
Use the following recommended options
with the pureQuery Configure utility and StaticBinder utility when
you prepare SQL statements to be run statically with pureQuery client
optimization.
Options for storing pureQuery data
When you run applications that are
enabled with pureQuery client optimization, you can specify the location
where pureQuery Runtime retrieves the runtime configuration information,
and pureQueryXML information. When you capture SQL data, you can specify
where the data is stored.
Recommendations for multiple schemas within a database
If you support multiple concurrent
development or test environments in the same system, your applications
might be written with unqualified table names. When unqualified table
names are used, multiple developers can execute concurrently against
multiple copies of the same database schema with different qualifier
names.
Applications that are moved to different application servers
You can move an application that is enabled with pureQuery
client optimization from one application server to another without
the need to recapture SQL statements that are run by the application.