7.5 Summarizing Indexes

 < Day Day Up > 



This concludes the discussion of what could be termed "Common Sense Indexing". Handling indexing in Oracle Database is somewhat based on indexing in any relational database. Indexing in a database should be as close as possible to indexing provided by the data model, particularly Referential Integrity indexing. If you have too much alternate and secondary indexing you may want to consider revisiting your data model, if this is possible. If your data model does not provide the basic structural functionality for attached applications then application requirements may require significant alteration to your data model. There is much to be said for building the data model with application functionality in mind. On the other hand, if your applications require large numbers of joins and additions to the data model it could be that performance may benefit substantially from creation of a separate reporting or data warehouse database. Highly active changeable concurrent environments such as OLTP databases and applications have very different requirements to that of any type of reporting or data warehouse functionality. The two simply do not mix very well. Mixing large quantities of small transactions in an OLTP database with large throughput of reporting and data warehouse activity can cause severe performance issues.

In the next chapter we will revert back to the study of how to perform SQL code tuning. So far in this book we have not dug too far into the internal specifics of tuning SQL code in Oracle Database. You should now have a basic knowledge of how to tune SQL code and build proper indexing in general. The next chapter will start to examine the explicit details of how to tune SQL code in Oracle Database.



 < Day Day Up > 



Oracle High Performance Tuning for 9i and 10g
Oracle High Performance Tuning for 9i and 10g
ISBN: 1555583059
EAN: 2147483647
Year: 2003
Pages: 164

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net