BackCover

---

Back Cover

Master the three parts of 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 nNormalization and dDe-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 in performance problems and is expensive to rectify. However, tuning of SQL code is generally cheaper than changing the data model. SQL code tend to be contained inside independent blocks within applications or stored procedures.

Physical database tuning involves hardware resource usage, networking and various other Oracle components 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

About the Author

Gavin Powell BSc., Comp.Sci., OCP has fifteen years of diverse experience in database administration and database development in both relational and object databases. His applications development experience is procedural and object-oriented and he also has some systems administration experience. He consults for software vendors, Internet .COMs (some of which unfortunately have met with their demise), accounting, banking, and financial services, the travel industry, construction, retail, mining, shipping, education and in a general advisory capacity.

---