For example, the batch accounts may use the database??™s
automatic login features, whereas the online users have to manually sign in. Your security plans
for the application must support both types of users.
Like the space requirements deliverable, security planning is an area in which the DBA??™s
involvement is critical. The DBA should be able to design an implementation that meets the
application??™s needs while fitting in with the enterprise database security plan.
Data Requirements
The methods for data entry and retrieval must be clearly defined. Data-entry methods must be
tested and verified while the application is in the test environment. Any special data-archiving
requirements of the application must also be documented because they will be application specific.
You must also describe the backup and recovery requirements for the application. These
requirements can then be compared to the enterprise database backup plans (see Chapter 11 for
guidelines). Any database recovery requirements that go beyond the site??™s standard will require
modifying the site??™s backup standard or adding a module to accommodate the application??™s needs.
Query Execution Plans
Execution plans are the steps that the database will go through while executing queries. They are
generated via the explain plan or set autotrace commands, as described in Chapter 8. Recording
the execution plans for the most important queries against the database will aid in planning
the index usage and tuning goals for the application.
Pages:
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250