Properties for client optimization

These descriptions explain the purpose for each of the pureQuery Runtime properties that you can set to determine how pureQuery captures SQL statements and runs those captured statements.
Not all pureQuery Runtime properties are supported for pureQuery client optimization. The following table lists the pureQuery Runtime properties that can be used pureQuery client optimization.
Table 1. pureQuery Runtime properties for client optimization
Property Description
allowDynamicSQL Specifies whether to allow an application to run dynamically any SQL statements that are not captured in a pureQueryXML file or that are captured but not bound.
capturedOnly Specifies whether to run only the SQL statements that are in the pureQueryXML file.
captureMode Specifies whether to capture information about SQL statements.
captureStatementBatchSQL Specifies whether to capture SQL DML statements that the application passes to a Statement.addBatch() method, up to the number of SQL statements (not including SELECT statements) that is specified by the maxNonParmSQL property.
enableDynamicSQLReplacement Specifies whether to run alternative SQL statements that were added to a pureQueryXML file and both the original statements and the alternative statements were not bound.
executionMode Specifies whether to run statically the SQL statements that have been previously captured and stored by pureQuery Runtime.
finalRepositoryProperties Specifies the location of the pureQuery properties used with a pureQuery-enabled application.
maxNonParmSQL Specifies the maximum number of non-parameterized SQL statements to capture. This option applies only when the value of captureMode is ON. When captureMode is OFF, pureQuery ignores this parameter.
maxStackTracesCaptured Specifies the maximum number of stack traces that are recorded for the definition point and the execution point for each SQL statement that you capture.
outputPureQueryXml Specifies a fully-qualified or relative path to and name of the file or files that the process of capturing SQL statements creates.
outputXmlRepository Specifies a database that contains a repository. The repository stores captured SQL data from an application enabled for pureQuery client optimization.
packagePrefixExclusions Specifies a pipe-separated list of domains and subdomains of the Java packages that you do not want to include in stack traces.
propertiesGroupId Specifies a runtime group ID in a repository that is created in a database. pureQuery Runtime uses the runtime group ID and the connection information that specifies the repository to either store SQL data captured from an application, or to retrieve pureQuery runtime configuration and pureQueryXML file information.
propertiesRefreshInterval Specifies the duration, in minutes, to wait before pureQuery client optimization checks the location of stored pureQuery data for changes to pureQuery properties or pureQueryXML data. When updates have been detected, pureQuery client optimization retrieves the updated pureQuery runtime properties and pureQueryXML data and uses the updated information.
pureQueryXml Specifies the fully-qualified or relative path to and name of a file that is to be created by the process of capturing SQL statements or that already exists as a result of that process.
repositoryRequired Specifies the pureQuery client optimization behavior if errors occur during retrieving or writing pureQuery data. If the pureQuery runtime properties and pureQueryXML data cannot be retrieved from the location specified by the finalRepositoryProperties property, or if the repository that stores captured SQL is not accessible.
sqlLiteralSubstitution Specifies whether perform literal substitution. pureQuery Runtime attempts to replace literal values in SQL statements with parameter markers and capture the parameterized versions of the statements.
stackTraceDepth Specifies the maximum number of stack trace entries that are recorded for each SQL statement. These entries are recorded in the pureQueryXML file.
traceFile Specifies the physical file to write the log into. You can use an absolute path or a path that is relative to the directory in which the pureQuery Log utility runs.
traceLevel Specifies the level of detail to write to the log file.

Feedback