16.10.2015 Views

Getting Startedwith pureQuery

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

160<br />

<strong>Getting</strong> Started with <strong>pureQuery</strong><br />

stack:<br />

Figure 8.5 - Middle tier monitoring information is graphically integrated with data<br />

server monitoring statistics in Optim Performance Manager.<br />

Extended Insight gives DBA’s insight into the application stack layers above the database, to solve<br />

data access problems quickly. Even packaged and framework applications using the prerequisite<br />

IBM JDBC or CLI drivers can take advantage of the additional client statistics provided via client<br />

monitoring.<br />

8.3.2 Identifying <strong>pureQuery</strong> Applications Using Extended Insight<br />

<strong>pureQuery</strong> applications can take special advantage of certain Extended Insight features. In<br />

addition to providing monitoring statistics from previously obscured stack layers, <strong>pureQuery</strong><br />

client monitoring also gives DBA’s important identifying information about <strong>pureQuery</strong> client<br />

applications.<br />

In Figure 8.1, the identity of applications issuing SQL is obscured from the DBA monitoring<br />

the database. They are identified to the DBA only as generic, dynamic, JDBC applications.<br />

If there are thousands of dynamic JDBC applications in the enterprise, this does not give<br />

the DBA enough information to quickly identify the application executing a problematic SQL<br />

statement. Java database drivers use one set of common dynamic packages to execute<br />

dynamic SQL. The end result is that most Java workloads are grouped into one large,<br />

shapeless, and obscure category by database monitors and workload management tools.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!