On databases that support static SQL, you can use the Runtime
Group Working Copy Editor to create packages in the database
from the SQL statements in the runtime group version pureQueryXML
data, and bind those packages to the database. Binding SQL statements
is one step in the process of managing pureQuery data for a version.
About this task
The
Runtime Group Working Copy Editor extracts
a working copy of the following pureQuery data to your workspace:
- The pureQueryXML data
- The pureQuery runtime configuration
- The bind options
- The configure options
- The captured SQL data
Procedure
To bind the SQL statements in the pureQueryXML data of
a runtime group version to a database:
- Open the Runtime Group Working Copy Editor:
- Right-click a runtime group, then click Manage Active
Version to manage the active version for a runtime group.
- Right-click a runtime group version, then click Manage to
manage a specific version.
The editor opens and is positioned to the
Steps page. The Steps page contains instructions to manage the runtime
group version.
- Click Bind the working copy of the pureQueryXML to
expand the bind section.
- Select a connection to use for binding the pureQueryXML
SQL statements.
- Click the Bind Properties link to
open the bind properties in the BindProps Editor. If needed,
modify the properties.
When binding SQL statements in the pureQueryXML
data for the runtime group version, the default properties for the
all packages created for the pureQueryXML data should be specified
in using the -defaultOptions option. If different
properties are needed for a specific package, specify the package-specific
options using the basePdqxml:packageName option.
The keyword base.pdqxml in the bindProps Editor
will be replaced with the actual file name before the StaticBinder
utility is invoked.
- Click Bind pureQueryXML to create
the packages from the SQL statements in the pureQueryXML data, and
bind the packages to the database. The StaticBinder utility
is invoked and the results are written to the Console view.
What to do next
Update the pureQuery data in the runtime group version
with the working copy of the pureQuery data.
After updating
the runtime group version pureQuery data, you can set the runtime
group version to active to make it available to an application enabled
with pureQuery client optimization.