Book Image

Oracle Database 11gR2 Performance Tuning Cookbook

By : Ciro Fiorillo
Book Image

Oracle Database 11gR2 Performance Tuning Cookbook

By: Ciro Fiorillo

Overview of this book

Oracle's Database offers great performance, scalability, and many features for DBAs and developers. Due to a wide choice of technologies, successful applications are good candidates to run into performance issues and when a problem arises it's very difficult to identify the cause and the right solution to the problem. The Oracle Database 11g R2 Performance Tuning Cookbook helps DBAs and developers to understand every aspect of Oracle Database that can affect performance. You will be guided through implementing the correct solution in a proactive way before problems arise, and how to diagnose issues on your Oracle database-based solutions. This fast-paced book offers solutions starting from application design and development, through the implementation of well-performing applications, to the details of deployment and delivering best-performance databases. With this book you will quickly learn to apply the right methodology to tune the performance of an Oracle Database, and to optimize application design and SQL and PL/SQL code. By following the real-world examples you will see how to store your data in correct structures and access and manipulate them at a lightning speed. You will learn to speed up sort operations, hack the optimizer and the data loading process, and diagnose and tune memory, I/O, and contention issues. The purpose of this cookbook is to provide concise recipes, which will help you to build and maintain a very high-speed Oracle Database environment.
Table of Contents (21 chapters)
Oracle Database 11gR2 Performance Tuning Cookbook
Credits
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
Index

Using subqueries


We often use subqueries in our SQL statements to nest more queries in one statement, using the results from an "inner" query to calculate other values.

In this recipe, we will see the use of subqueries for getting only a subset of records, demonstrating the constructs (NOT) EXISTS and (NOT) IN, highlighting the semantic difference between them (and when to choose one type of statement or the other).

How to do it...

The following steps will demonstrate the use of subqueries:

  1. Connect to the SH schema:

    CONNECT sh@TESTDB/sh
    SET AUTOT TRACE EXP STAT
    
  2. Select a table using the IN operator:

    SET AUTOT TRACE EXP STAT
    SELECT AMOUNT_SOLD FROM sh.SALES S
    WHERE S.CUST_ID IN (
      SELECT C.CUST_ID FROM sh.CUSTOMERS C
      WHERE C.CUST_CREDIT_LIMIT IN (10000, 11000, 15000)
    );
    
  3. Rewrite the same query using the EXISTS construct:

    SELECT AMOUNT_SOLD FROM sh.SALES S
    WHERE EXISTS (
      SELECT NULL FROM sh.CUSTOMERS C
      WHERE S.CUST_ID = C.CUST_ID
      AND C.CUST_CREDIT_LIMIT IN (10000, 11000, 15000)
    );
    
  4. Select...