Cargando…
Oracle SQL tuning : pocket reference /
One of the most important challenges faced by Oracle database administrators and Oracle developers is the need to tune SQL statements so that they execute efficiently. Poorly tuned SQL statements are one of the leading causes of substandard database performance and poor response time. SQL statements...
| Clasificación: | Libro Electrónico |
|---|---|
| Autor principal: | |
| Formato: | Electrónico eBook |
| Idioma: | Inglés |
| Publicado: |
Beijing ; Farnham :
O'Reilly,
2002.
|
| Temas: | |
| Acceso en línea: | Texto completo (Requiere registro previo con correo institucional) |
Tabla de Contenidos:
- Oracle SQL Tuning Pocket Reference; 1.1.2. Caveats; 1.1.3. Conventions; 1.1.4. What&s New in Oracle9i; 1.2. The SQL Optimizers; 1.2.1.2. What the RBO rules don&t tell you #2; 1.2.1.3. What the RBO rules don&t tell you #3; 1.2.1.4. What the RBO rules don&t tell you #4; 1.2.1.5. What the RBO rules don&t tell you #5; 1.2.1.6. What the RBO rules don&t tell you #6; 1.2.1.7. What the RBO rules don&t tell you #7; 1.2.2. Understanding the Cost-Based Optimizer; 1.2.2.2. Tuning prior to releasing to production; 1.2.2.3. Inner workings of the cost-based optimizer
- 1.2.2.4. EXPLAIN PLAN for the cost-based optimizer1.2.3. Some Common Optimizer Misconceptions; 1.2.4. Which Optimizer to Use?; 1.3. Rule-Based Optimizer Problems and Solutions; 1.3.2. Problem 2: Incorrect Index; 1.3.3. Problem 3: Incorrect Driving Index; 1.3.4. Problem 4: Using the ORDER BY Indexand not the WHERE Index; 1.4. Cost-Based Optimizer Problems and Solutions; 1.4.2. Problem 2: Analyzing with Wrong Data; 1.4.2.2. When to analyze; 1.4.3. Problem 3: Mixing the Optimizers in Joins; 1.4.4. Problem 4: Choosing an Inferior Index; 1.4.5. Problem 5: Joining Too Many Tables
- 1.4.6. Problem 6: Incorrect INIT.ORA Parameter Settings1.5. Problems Common to Rule and Cost with Solutions; 1.5.2. Problem 2: Indexes Are Missing or Inappropriate; 1.5.2.2. Adding columns to indexes; 1.5.2.3. Should I index small tables?; 1.5.3. Problem 3: Use of Single-Column Index Merge; 1.5.4. Problem 4: Misuse of Nested Loop, Sort Merge, or Hash Join; 1.5.5. Problem 5: Misuse of IN, EXISTS, NOT IN, NOT EXISTS, or Table Joins; 1.5.5.2. Which is faster, IN or EXISTS?; 1.5.6. Problem 6: Unnecessary Sorts; 1.5.6.2. Consider using an index to avoid a sort
- 1.5.7. Problem 7: Too Many Indexes on a Table1.5.8. Problem 8: Use of OR Instead of UNION; 1.5.9. Problem 9: Tables and Indexes with Many Deletes; 1.5.10. Other Problems: Heavy Usage of Views; 1.5.11. Other Problems: Joining Too Many Tables; 1.6. Handy SQL Tuning Tips; 1.6.2. Identify Long-Running SQL Statements; 1.6.3. Use DECODE for IF/ELSE Selection; 1.6.4. Encourage Bind Variables; 1.7. Using SQL Hints; 1.7.2. Using Hints in Views; 1.7.3. Available Hints; 1.8. Using DBMS_STATS to Manage Statistics; 1.8.2. Copying Statistics Using DBMS_STATS; 1.8.3. Manipulating Statistics Using DBMS_STATS
- 1.8.4. Reverting to Previous Statistics1.9. Using Outlines for Consistent Execution Plans; 1.9.1.2. Recording outlines for all of a session&s SQL; 1.9.1.3. Recording outlines for the whole system; 1.9.2. Enabling Outlines; 1.9.2.2. Enabling outlines for the whole system; 1.9.3. Managing Outlines; 1.9.3.2. Transferring outlines between databases; 1.9.3.3. Dealing with literals