Database Reference
In-Depth Information
When your analysis points to a small number of SQL statements or a limited piece of PL/SQL code,
you've found the part of your application that needs optimization, and there's likely a straightforward
way of fixing it. Otherwise, a response time distributed over a large number of SQL statements or
over a large part of the PL/SQL code usually means the problem is due to design decisions; complete
reengineering could be necessary. If the design itself isn't a problem, then it's likely that the machine
running the application is undersized.
The ultimate, straightforward aim of Part II is to introduce and employ a methodology that avoids
guesswork and establishes beyond any doubt where a bottleneck is in an underperforming application.
Included in that aim is the gathering of essential information needed to progress into Parts III and IV.
