Relational Database Index Design and the Optimizers (Hardcover)

Tapio Lahdenmaki, Mike Leach

  • 出版商: Wiley
  • 出版日期: 2005-07-01
  • 售價: $3,780
  • 貴賓價: 9.5$3,591
  • 語言: 英文
  • 頁數: 328
  • 裝訂: Hardcover
  • ISBN: 0471719994
  • ISBN-13: 9780471719991
  • 相關分類: SQL
  • 相關翻譯: 數據庫索引設計與優化 (簡中版)
  • 立即出貨 (庫存=1)





The most common reason for performance problems with database applications is inadequate indexing.
This book covers index design, one aspect of database tuning. It will teach the reader how to improve the performance of relational databases (IBM DB2, Oracle, Microsoft SQL Server and others) with indexes designed for current hardware (gigabytes of central storage, large disk drives with RAID 5, etc...).
Other common reasons are poor table design, SQL optimizer and long lock waits, all covered in this book. This is a very important topic for database specialists and application developers but most database product manuals and books cover indexing very briefly - perhaps because index design issues are not product specific. Unlike table design, index design can be relatively easily improved while the application is already in production.


Table of Contents:


1. Introduction.

Another Book About SQL Performance!

Inadequate Indexing.

Myths and Misconceptions.

2. Table and Index Organization.


Index Rows.

Index Structure.

Table Row.

Buffer Pools and Disk I/Os.

Hardware Specifics.

DBMS Specifics.

3. SQL Processing.



Optimizers and Access Paths.

Filter Factors.

Materializing the Result Rows.


4. Deriving the Ideal Index for a SELECT.


Basic Assumptions for Disk and CPU Times.

Inadequate Index.

Three-Star Index—The Ideal Index for a SELECT.

Algorithm to Derive the Best Index for a SELECT.

Ideal Index for Every SELECT?

Cost of an Additional Index.



5. Proactive Index Design.

Detection of Inadequate Indexing.

Basic Question (BQ).

Quick Upper-Bound Estimate (QUBD).

Cheapest Adequate Index or Best Possible Index: Example 1.

Cheapest Adequate Index or Best Possible Index: Example 2.

When to Use the QUBE.

6. Factors Affecting the Index Design Process.

I/O Time Estimate Verification.

Multiple Thin Index Slices.

Difficult Predicates.

Filter Factor Pitfall.

Filter Factor Pitfall Example.


7. Reactive Index Design.


EXPLAIN Describes the Selected Access Paths.

Monitoring Reveals the Reality.

LRT-Level Exception Monitoring.

Call-Level Exception Monitoring.

DBMS-Specific Monitoring Issues.


8. Indexing for Table Joins.


Two Simple Joins.

Impact of Table Access Order on Index Design.

Basic Joint Question (BJQ).

Predicting the Table Access Order.

Merge Scan Joins and Hash Joins.

Nested-Loop Joins Versus MS/HJ and Ideal Indexes.

Joining More Than Two Tables.

Why Joins Often Perform Poorly.

Designing Indexes for Subqueries.

Designing Indexes for Unions.

Table Design Considerations.


9. Star Join Considerations.


Indexes on Dimension tables.

Huge Impact of the Table Access Order.

Indexes on Fact Tables.

Summary Tables.

10. Multiple Index Access.


Index ANDing.

Index ORing.

Index Join.


11. Indexes and Reorganization.

Physical Structure of a B-Tree Index.

How the DBMS Finds an Index Row.

What Happens When a Row IS Inserted?

Are Leaf Page Splits Serious?

When Should an Index Be reorganized?

Volatile Index Columns.

Long Index Rows.

Example: Order-Sensitive Batch Job.

Table Rows Stored in Leaf Pages.

Cost of Index Reorganization.

Split Monitoring.


12. DBMS-Specific Indexing Restrictions.


Number of Index Columns,

Total Length of the Index Columns.

Variable-Length Columns.

Number of Indexes per Table.

Maximum Index Size.

Index Locking.

Index Row Suppression.

DBMS Index Creation Examples.

13. DBMS-Specific Indexing Options.


Index Row Suppression.

Additional Index Columns After the Index Key.

Constraints to Enforce Uniqueness.

DBMS Able to Read an Index in Both Directions.

Index Key Truncation.

Function-Based Indexes.

Index Skip Scan.

Block Indexes.

Data-Partitioned Secondary Indexes.


14. Optimizers Are Not Perfect.


Optimizers Do Not Always See the Best Alternative.

Optimizers’ Cost Estimates May Be Very Wrong.

Cost Estimate Formulas.

Do Optimizer Problems Affect Index Design?


15. Additional Estimation Considerations.

Assumptions Behind the QUBE Formula.

Nonleaf Index Pages in Memory.

When the Actual Response Time Can Be Much Shorter Than the QUBE.

Estimating CPU Time (CQUBE).

CPU Estimation Examples.

16. Organizing the Index Design Process.


Computer-Assisted Index Design.

Nine Steps Toward Excellent Indexes.