This may require the creation and
maintenance of materialized views or reporting tables. That maintenance is, of course, extra work
for the database and DBA to perform??”but it is performed in batch mode and does not directly
affect the end user. The end user, on the other hand, benefits from the ability to perform the query
faster. The database as a whole will perform fewer logical and physical reads because the accesses
to the base tables to populate and refresh the materialized views are performed infrequently when
compared to the end-user queries against the views.
Avoid Repeated Connections to the Database
Opening a database connection may take more time than the commands you execute within
that connection. If you need to connect to the database, keep the connection open and reuse
the connection. See Chapter 15 for more information on Oracle Net and optimizing database
connections.
One application designer took normalization to the extreme, moving all code tables into their
own database. As a result, most operations in the order-processing system repeatedly opened
database links to access the code tables, thus severely hampering the performance of the application.
Again, tuning the database initialization parameters is not going to lead to the greatest performance
benefit; the application is slow by design.
Use the Right Indexes
In an effort to eliminate physical reads, some application developers create numerous indexes
on every table.
Pages:
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232