ABSTRACT
The techniques discussed in Part II are sophisticated and useful in many common scenarios. However, they take an offline approach to the physical design problem and still leave significant decisions to database applications (DBAs). Specifically, DBAs need to explicitly identify representative workloads and feed them to tuning tools. DBAs are also expected to guess when a tuning session is needed and when to deploy recommendations. Naturally, this is not a one-time process, but instead DBAs continuously monitor, diagnose, and tune database installations.
