Generating them prior to production
implementation will simplify tuning efforts and identify potential performance problems before
the application is released. Generating the explain plans for your most important queries will
also facilitate the process of performing code reviews of the application.
If you are implementing a third-party application, you may not have visibility to all the SQL
commands the application is generating. As described in Chapter 8, you can Oracle??™s automated
tuning and monitoring utilities to identify the most resource-intensive queries performed between
two points in time; many of the new automated tuning features introduced in Oracle Database
10g are enhanced in Oracle Database 11g, such as the capability to store Automatic Workload
Repository (AWR) baselines in addition to automatically create SQL profiles.
Acceptance Test Procedures
Developers and users should very clearly define what functionality and performance goals must
be achieved before the application can be migrated to production. These goals will form the
foundation of the test procedures that will be executed against the application while it is in the
test environment.
The procedures should also describe how to deal with unmet goals. The procedures should
very clearly list the functional goals that must be met before the system can move forward. A
second list of non-critical functional goals should also be provided. This separation of functional
capabilities will aid in both resolving scheduling conflicts and structuring appropriate tests.
Pages:
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251