Ships from: Phoenix, MD
Usually ships in 1-2 business days
Ships from: Chatham, NJ
Usually ships in 1-2 business days
Ships from: acton, MA
Usually ships in 1-2 business days
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
Audience: Oracle users, Developers, Database Administrators, Consultants and Corporate professionals.
Data Model Tuning: emphasis on both relational and object model tuning for Java and other object designed Internet OLTP applications. SQL Code Tuning: tune SQL statements both with and without using Optimizer query plans. Physical and Configuration Tuning: creating a well-balanced physical and configuration architecture at initial Oracle installation; bottleneck tuning.
Anonymous
Posted Fri Jan 09 00:00:00 EST 2004
This is a thorough, even scholarly, book by Mr. Powell. He has obviously spent a great deal of effort to explain clearly and concisely some of the most important aspects of Oracle performance tuning. Some areas that I found especially interesting were his explanations of the various lock mechanisms in the Oracle engine. The book is also very extensively illustrated with examples of execution plans, and many SQL examples. Another area of great use is the explanation of Partitioning¿an area that most of us find very confusing. Mr Powell wisely points out the advisability of developers getting the design right in the first place¿preventative medicine, as it were. The book is also interspersed with explanations of 10g additions. For instance, he shows the improvements to the Wait Event interface starting with 10g. Toward the end of the book, Gavin illustrates how to use the interesting utility Statspack. All in all, a very nice exposition of a very tough subject.
Was this review helpful? Yes NoThank you for your feedback. Report this reviewThank you, this review has been flagged.
Overview
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...