Editing your application can invalidate stack traces that are recorded in the pureQueryXML file.
Property | Setting | Effect |
---|---|---|
captureMode | ON | Causes pureQuery to capture statements when you run those statements in an application. |
For
a non-clustered application, if you do not want to preserve the pureQueryXML
file from being written to: pureQueryXml |
The name and path of the original pureQueryXML file. | When
you run your application with the settings that are in the table,
pureQuery checks whether a given SQL statement is already in the pureQueryXML
file for the connection that the statement must run against. Then,
pureQuery performs one of these actions:
|
For
a non-clustered application, if you use the original pureQueryXML
file as an input file and want only to capture statements that you
did not yet capture: pureQueryXml outputPureQueryXml |
Setting
for pureQueryXml: The name and path of the original pureQueryXML file. Setting for outputPureQueryXml: file-name.pdqxml or file-name.xml |
When you run your
application with the settings that are in the table, pureQuery checks
whether a given SQL statement is already in the pureQueryXML file
(that you specified with the pureQueryXml property)
for the connection that the statement must run against. Then, pureQuery
performs one of these actions:
After you produce the output pureQueryXml file, you can merge it together with the original file. |
For
a clustered application, using a pureQueryXML file that is the result
of the merge of the pureQueryXML files that you created when you last
captured statements from the clustered application: pureQueryXml outputPureQueryXml |
Setting for pureQueryXml: The name and path of the pureQueryXML file that resulted from the merge. Setting for outputPureQueryXml: file-name.pdqxml or file-name.xml |
When you run your application instances with the settings that are in the table, pureQuery checks whether a given SQL statement is already in the pureQueryXML file that you specified with the pureQueryXml property. Then, pureQuery performs one of these actions:
|
This table does not show properties that you can leave at their default values or other properties that you might want to use.
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 capturing and running restricted sets of SQL statements dynamically for information about how and where to set these properties.