Getting Startedwith pureQuery
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
164<br />
<strong>Getting</strong> Started with <strong>pureQuery</strong><br />
• <strong>pureQuery</strong>Xml package name and statement entry id<br />
• Information about the call stack of the statement at the time the metadata was<br />
created (when the SQL was captured)<br />
This information, when provided to the application developer, can be used to jump-start<br />
problem resolution for monitored applications associated with <strong>pureQuery</strong>Xml.<br />
8.5 Summary<br />
Extended Insight provides visibility into, and knowledge about, the application stack that<br />
was previously unavailable to DBAs and others trying to monitor and troubleshoot multitiered,<br />
data access applications. It provides the ability to pinpoint specific java applications<br />
as they are running, regardless of whether they are executing statically or dynamically. For<br />
each identified, client-monitored workload, result set processing time, driver time, network<br />
time, and server time, along with a variety of additional metrics, can be examined for any<br />
group of transactions or statements. This allows the application-centric DBA to identify,<br />
rule out, and pinpoint problems anywhere in the data access application stack, not only<br />
within the database. Importantly, <strong>pureQuery</strong> monitoring can increase visibility into the data<br />
access stack for existing applications, running in existing frameworks, without changing<br />
application code. <strong>pureQuery</strong> applications with <strong>pureQuery</strong>Xml registered with Optim<br />
Performance Manager benefit from the deepest problem determination support, and plain<br />
JDBC or CLI applications also benefit from increased visibility through Extended Insight.<br />
When <strong>pureQuery</strong> application metadata is registered with Optim Performance Manager, the<br />
monitor can identify the issuing <strong>pureQuery</strong> application for many <strong>pureQuery</strong>-issued SQL<br />
statements, down to the specific application source line or the specific capture snapshot,<br />
reducing resolution and fix time. Extended Insight provides a previously missing link across<br />
the persistence layer and data access frameworks. It fits seamlessly between existing<br />
application monitor coverage zones and traditional application and database monitoring<br />
tools, to monitor currently obscured layers of the data access stack, reducing problem<br />
determination time and increasing monitoring effectiveness.<br />
8.6 Review Questions<br />
1. What are some common problems faced by DBA’s in a multi-tiered environment?<br />
2. What is a native <strong>pureQuery</strong> application?<br />
3. True or false: Extended Insight integrates seamlessly with database-centric<br />
monitor data?<br />
4. What is the necessary step required before <strong>pureQuery</strong> application metadata is<br />
useful to the DBA performing monitoring activities?
Change language