Linked e-resources
Details
Table of Contents
Foreword by Watson; Foreword by Gosejacob; Foreword by Schwinn; Preface; Contents; 1: Introduction; 1.1 Aims and Target Groups; 1.2 An Overview of the Book; 1.3 Acknowledgments; 2: Some Thoughts on the Term ``SQL Tuning;́́ 2.1 SQL Tuning: Definitions and Objectives; 2.2 SQL Tuners; 2.2.1 Oracle; 2.2.2 Developer; 2.2.3 Database Administrator; 3: Minimum Minimorum on the Subject of the ``Execution Plan;́́ 3.1 Can You Read Execution Plans?; 3.2 Some Important Details; 3.2.1 Sections of the Execution Plan; 3.2.1.1 Plan; 3.2.1.2 Query Block Name/Object Alias; 3.2.1.3 Outline Data
3.2.1.4 Peeked Binds3.2.1.5 Predicate Information; 3.2.1.6 Column Projection Information; 3.2.1.7 Remote SQL Information; 3.2.1.8 Note; 3.2.2 Optimizer Estimations and Costs; 3.2.3 Runtime Statistics; 3.3 Summary; 4: Approaches to Formal SQL Tuning; 4.1 The Objective: Effective SQL Tuning; 4.2 The Principle: Elimination of ``Brakes ́́in the Execution Plan; 4.3 The Method: Analysis of Runtime Statistics in the Execution Plan; 4.4 The Main Criterion: The Runtime Statistic ``Cardinality;́́ 4.5 The Procedure: An Iterative Process; 4.6 The Guideline: Tuning Without Changing the SQL Statement
5: Bottlenecks in the Execution Plan5.1 ``Local ́́Problems in the Execution Plan; 5.1.1 A Missing Index; 5.1.2 A Nonselective Index; 5.1.3 An Index with a Large Clustering Factor; 5.1.4 A Sparse Index; 5.1.5 Nested Loop Join Instead of Hash Join and Vice Versa; 5.2 ``Global ́́Problems in the Execution Plan; 5.2.1 Formal Rules for Changing the Table Order in a Join; 5.2.2 Joins with a Low Number of Hits; 5.2.3 Joins with a Large Hit Quantity; 5.3 Summary; 6: Procedure of Formal SQL Tuning; 7: Practical Experience with Formal SQL Tuning; 7.1 Hannoś Experience
7.1.1 Statistics on Problem Categories7.1.2 A Small Synthetic Test Case in Respect of a Nonselective Index; 7.1.3 Practical Example; 7.1.3.1 The First Improvement; 7.1.3.2 The Second Improvement; 7.2 Victorś Experience; 7.2.1 The First Practical Example; 7.2.2 The Second Practical Example; 8: Closing Remarks; Appendix: Application of the Formal Principle for the Analysis of Performance Problems After an Oracle Migration; Literature
3.2.1.4 Peeked Binds3.2.1.5 Predicate Information; 3.2.1.6 Column Projection Information; 3.2.1.7 Remote SQL Information; 3.2.1.8 Note; 3.2.2 Optimizer Estimations and Costs; 3.2.3 Runtime Statistics; 3.3 Summary; 4: Approaches to Formal SQL Tuning; 4.1 The Objective: Effective SQL Tuning; 4.2 The Principle: Elimination of ``Brakes ́́in the Execution Plan; 4.3 The Method: Analysis of Runtime Statistics in the Execution Plan; 4.4 The Main Criterion: The Runtime Statistic ``Cardinality;́́ 4.5 The Procedure: An Iterative Process; 4.6 The Guideline: Tuning Without Changing the SQL Statement
5: Bottlenecks in the Execution Plan5.1 ``Local ́́Problems in the Execution Plan; 5.1.1 A Missing Index; 5.1.2 A Nonselective Index; 5.1.3 An Index with a Large Clustering Factor; 5.1.4 A Sparse Index; 5.1.5 Nested Loop Join Instead of Hash Join and Vice Versa; 5.2 ``Global ́́Problems in the Execution Plan; 5.2.1 Formal Rules for Changing the Table Order in a Join; 5.2.2 Joins with a Low Number of Hits; 5.2.3 Joins with a Large Hit Quantity; 5.3 Summary; 6: Procedure of Formal SQL Tuning; 7: Practical Experience with Formal SQL Tuning; 7.1 Hannoś Experience
7.1.1 Statistics on Problem Categories7.1.2 A Small Synthetic Test Case in Respect of a Nonselective Index; 7.1.3 Practical Example; 7.1.3.1 The First Improvement; 7.1.3.2 The Second Improvement; 7.2 Victorś Experience; 7.2.1 The First Practical Example; 7.2.2 The Second Practical Example; 8: Closing Remarks; Appendix: Application of the Formal Principle for the Analysis of Performance Problems After an Oracle Migration; Literature