Required settings for capturing SQL statements for the first time when using client optimization

With these settings, pureQuery runs all of the SQL statements dynamically and captures them in a pureQueryXML file.

This table does not show properties that you can leave at their default values or other properties that you might want to use.

Table 1. Required settings for capturing SQL statements in a new or empty pureQueryXML file
Property Setting Effect
captureMode ON Causes pureQuery to capture statements when you run those statements in an application. The statements run dynamically because the property executionMode is set to DYNAMIC by default.
For a non-clustered application:
pureQueryXml or outputPureQueryXml
file-name.pdqxml or file-name.xml Causes pureQuery to capture statements, and information related to those statements, in the file that you specify. There is no default value for these properties. You must use one of these properties or the other.
For a clustered application:
outputPureQueryXml
file-name$X.pdqxml or file-name$X.xml Causes pureQuery to capture statements, and information related to those statements, from each application instance in the cluster to files specific to each instance. pureQuery generates the names of the files because of the $X, which pureQuery replaces with the ID of the class loader for the instance and with a timestamp. The file-name prefix is optional.

Use the Merge utility to merge these files together.

Here is a complete list of the properties that you can use when capturing SQL statements:

You can also set logging properties. See Descriptions of properties for logging and tracing.

See How to set properties for client optimization for information about how and where to set these properties.


Feedback