Getting Startedwith pureQuery

308
Getting Started with pureQuery
3. The StaticBinder utility binds four packages in the database, one at each of four
isolation levels. Each package contains all of the SQL statements in the interface.
4. The names of the packages are the root package name of the interface, generally
with 1, 2, 3, or 4 appended to indicate the isolation level. The root package name
of an interface is specified with the -rootPkgName option to the Generator utility,
and it is stored in the identifier field in the implementation class. If the option
-rootPkgName is not specified, the Generator utility chooses a name that is
based on the name of the interface.
5. The names of the packages are the base package names of the statement sets in
the pureQueryXml file, generally with 1, 2, 3, or 4 appended to indicate the
isolation level. The base package name of a statement set is the value in the
name attribute of its package element. For pureQueryXml files that are processed
with the Configure utility, the root package name is specified to the Configure utility
with the option -rootPkgName, and the utility uses the root package name to
create the base package names of the statement sets.
6. A.
7. D.
8. Specify the name of the file, followed by a colon, followed by the base package
name of the statement set. For example,
C:\path\captureFile.pdqxml:MYPKGA
9. .ear, .jar, .war, .zip
10. B.
11. True.
Chapter 8
1. Common problems faced by DBAs in a multi tiered environment include lack of
information about performance statistics in the middle tier, and inability to identify
the applications executing problematic SQL.
2. A native pureQuery application is one written in pureQuery annotated method style
or using pureQuery development tooling that produces similar source metadata,
such as a Data Web Service.
3. True. Extended Insight data integrates seamlessly with database-centric monitor
data.
4. Before application metadata can be useful for monitoring and problem
determination, it must be registered with OPM.