Getting Startedwith pureQuery

82
Getting Started with pureQuery
Figure 4.8 - Database Packages Page
4.2.4 Enhanced impact analysis within database applications
With the SQL Outline, you can gain insight into what parts of your application use certain
tables, columns or views by determining the objects referenced in the statements. The
database design often goes through changes during the application development stage.
The inability to gain insight into many different areas of an application can make simple
changes to a schema or a table a risky operation, as those changes may adversely affect
other parts of the application without the knowledge of the user.
The impact analysis features of the pureQuery tooling help DBAs and developers to work
together to come up with database changes that would have the least impact on an
application, thus mitigating risks.
In the Database page, for example, you can gain insight into how much your application
might need to change if a given table or view were to change. By expanding the table, you
can gain insight into all the SQL statements affected and their location within your
application. In the case of a change in a table’s column, such as a name change or simply
by dropping it, you can use the SQL Outline filter and provide the name of the affected
column to view all the affected statements. The filter can either be invoked by right-clicking
anywhere on the SQL Outline and selecting Filter… from the context menu or by clicking
on the inverted triangle on the toolbar and selecting Filter…
For example, if you want to assess which statements are impacted by dropping the BONUS
column on the EMPLOYEE table to then go to the application and change the code where
necessary, you would use the filter as shown in Figure 4.9. You can see the statements
that use the BONUS column only and narrow down to the specific place where those