Oracle High Performance Tuning For 9i And 10g

Oracle High Performance Tuning for 9i and 10g

There are three parts to tuning an Oracle database: data modeling, SQL code tuning and physical database configuration. A data model contains tables and relationships between tables. Tuning a data model involves normalization and de-normalization. Different approaches are required depending on the application, such as OLTP or a Data Warehouse. Inappropriate database design can make SQL code impossible to tune. Poor data modeling can have a most profound effect on database performance since all SQL code is constructed from the data model. Poorly written SQL code is often a culprit of performance problems and is expensive to rectify. However, tuning of SQL code is generally cheaper than changing the data model. SQL code tends to be contained inside independent blocks within applications or stored procedures. Physical database tuning involves hardware resource usage, networking and various other Oracle things such as configuration and file distribution. Physical configuration is often a culprit of poor performance where Oracle is installed with defaults, and never altered by an expert. *Includes all three aspects of Oracle database tuning: data model tuning, SQL & PL/SQL code tuning, physical plus configuration tuning *Contains experienced guidance and real-world examples using large datasets *Emphasizes development as opposed to operating system perspective

Oracle Data Warehouse Tuning for 10g

"This book should satisfy those who want a different perspective than the official Oracle documentation. It will cover all important aspects of a data warehouse while giving the necessary examples to make the reading a lively experience. - Tim Donar, Author and Systems Architect for Enterprise Data WarehousesTuning a data warehouse database focuses on large transactions, mostly requiring what is known as throughput. Throughput is the passing of large amounts of information through a server, network and Internet environment, backwards and forwards, constantly! The ultimate objective of a data warehouse is the production of meaningful and useful reporting, from historical and archived data. The trick is to make the reports print within an acceptable time frame.A data model contains tables and relationships between tables. Tuning a data model involves Normalization and Denormalization. Different approaches are required depending on the application, such as OLTP or a Data Warehouse. Inappropriate database design can make SQL code impossible to tune. Poor data modeling can have a most profound effect on database performance since all SQL code is constructed from the data model.* Takes users beyond basics to critical issues in running most efficient data warehouse applications* Illustrates how to keep data going in and out in the most productive way possible* Focus is placed on Data Warehouse performance tuning

Oracle High Performance Tuning For 9i And 10g