After a database administrator creates a repository by using the ManageRepository utility, different applications can use pureQuery data that is stored in a repository. The pureQuery data for each application is stored in a separate runtime group. Multiple versions of the pureQuery data can be stored within each runtime group.
SQL data that is captured from an application can be stored either in a file or in the repository that is specified by the finalRepositoryProperties property. If the outputPureQueryXml property is retrieved from the location that is specified by the finalRepositoryProperties property, then the captured data is written to the file. If the outputXmlRepository property is retrieved from the location that is specified by the finalRepositoryProperties property, then the captured SQL data is written to a repository.
In a repository, one runtime group stores the pureQuery information that is used with one application. Each runtime group contains runtime group versions that store different versions of the pureQuery data used by pureQuery client optimization. Only one version of a runtime group can be active at a time. The pureQuery Runtime uses only the pureQuery data from the active runtime group version.
Repository information | Description | Example file name |
---|---|---|
pureQueryXML data | SQL statements and information that is related to the SQL statements. The information can be used by the pureQuery Runtime to control the execution of SQL statements. The StaticBinder utility uses the SQL statements to create packages and binds the packages in a database that supports static SQL. | caputure.pdqxml |
Options for configuration | Options that are used by the Configure utility to process the SQL statements in the pureQueryXML file. The Configure utility prepares the SQL statements in the pureQueryXML file for use by the StaticBinder utility and pureQuery Runtime. | default.genProps |
Options for bind | Options that are used by the StaticBinder utility to create packages and bind the packages from the SQL statements in the pureQueryXML data. | default.bindProps |
Runtime properties | Properties that are used by pureQuery Runtime to control execution of the SQL statements for an application. | pdq.properties |
Captured SQL data | SQL statements and SQL-related information, such as special register, stack trace, and performance, that is captured when using pureQuery client optimization.* | capture.pdqxml* |
* This information must be processed by the Configure utility before it can be used by pureQuery client optimization to execute SQL statements statically. Sets of captured SQL data can be combined by using the Merge utility. The workbench uses the Configure and Merge utilities to process the captured SQL data.
You assign a runtime group ID to each runtime group you create in the repository. When you configure an application to use pureQuery client optimization, you use the finalRepositoryProperties and propertiesGroupId properties specify the repository and the runtime group ID that pureQuery Runtime uses to retrieve the pureQuery runtime properties from the repository. When an application that is enabled with pureQuery client optimization is configured to use the information from a runtime group, the information from the active version is used with pureQuery Runtime to manage the SQL that is issued by the application.