Chapter 7. Reactive Index Design

  1. Tapio Lahdenmäki,
  2. Michael Leach

Published Online: 27 JAN 2005

DOI: 10.1002/0471721379.ch7

Relational Database Index Design and the Optimizers: DB2, Oracle, SQL Server, et al.

Relational Database Index Design and the Optimizers: DB2, Oracle, SQL Server, et al.

How to Cite

Lahdenmäki, T. and Leach, M. (2005) Reactive Index Design, in Relational Database Index Design and the Optimizers: DB2, Oracle, SQL Server, et al., John Wiley & Sons, Inc., Hoboken, NJ, USA. doi: 10.1002/0471721379.ch7

Author Information

  1. Smlednik, Slovenia, Shrewsbury, England

Publication History

  1. Published Online: 27 JAN 2005
  2. Published Print: 24 JUN 2005

ISBN Information

Print ISBN: 9780471719991

Online ISBN: 9780471721376

SEARCH

Keywords:

  • EXPLAIN;
  • index design;
  • access paths;
  • local response time;
  • LRT;
  • exception monitoring;
  • LRT-level exception monitoring;
  • transactions;
  • SQL problems;
  • spike reports;
  • bubble charts;
  • culprits;
  • victims;
  • promising culprits;
  • unpromising culprits;
  • tuning potential;
  • call-level exception monitoring;
  • monitoring comparison;
  • slow SQL calls;
  • DBMS specific monitoring;
  • SQL Server;
  • Oracle;
  • DB2 for z/OS

Summary

The role of the EXPLAIN function, and how it may be used during the index design process to describe the selected access paths. How to use LRT-level exception monitoring to identify transaction SQL problems by the use of spike reports which identify individual problems. The use of bubble charts to identify and analyze culprits and victims; distinguishing between promising and unpromising culprits to focus on the major potential benefits to be obtained - the tuning potential. How to use Call-level exception monitoring and a comparison with LRT-level. Finding slow SQL calls. DBMS specific monitoring issues.