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.

4<br />

Chapter 4 - <strong>pureQuery</strong> tooling Views<br />

In the following chapters you will learn how you can use the Client Optimizer feature of the<br />

<strong>pureQuery</strong> runtime to collect SQL statements from your application (Chapter 9) and then<br />

use the Static Binder utility (Chapter 10) to bind those statements into DB2 packages to<br />

gain better performance and a better authorization model for DB2 applications. Optim Data<br />

Studio’s (ODS) <strong>pureQuery</strong> tooling includes a set of features to assist you in performing<br />

these tasks faster and more easily whether you are a developer or an application-centric<br />

database administrator (DBA).<br />

4.1 <strong>pureQuery</strong> tooling: The big picture<br />

The <strong>pureQuery</strong> tooling from ODS provides a set of views and editors to help you optimize<br />

your new or existing applications (JPA, Hibernate, JDBC, <strong>pureQuery</strong> API) without changing<br />

a single line of code. The tooling includes problem isolation and impact analysis<br />

capabilities through the introduction of the SQL Outline view and the <strong>pureQuery</strong> Analysis<br />

view.<br />

The SQL Outline view gives developers the ability to drill down into the application to find<br />

where a specific SQL statement was executed. It improves the collaboration between<br />

DBAs and developers, for example, by allowing developers to quickly and easily gather<br />

and export all statements into a file for the DBA to analyze and give feedback:<br />

Figure 4.1 - SQL Outline View

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

Saved successfully!

Ooh no, something went wrong!