« An Application Tuning Case Study: The Deadly Deadlock | Main | Best Practices For Custom Order Entry Workflow Design »

A SQL Tuning Case Study: Could we K.I.S.S. Please?

                                         direct shot:

They say, it pays to K.I.S.S (Keep It Simple and Smart).
The simplest ideas are the greatest ideas.This philosophy also applies to sql
coding when we tell the oracle SQL engine what to fetch and how
to fetch it (Indirectly). There are great rewards for simplistic thinking.



Lets discuss this principle through a case study in which the user was
trying to fetch very simple data through an over-kill query, involving 
RA_* views which were internally using some of the same tables. The SQL
engine was therefore just trying to fetch and filter too much data from
the
same sources. It was not certainly efficient.



In this case study, we see how its important to understand the "Why" of
a query, rather than the "How" of a query. Many times, just rethinking
the whole approach pays great dividends.

Read the entire case study here...


TrackBack

TrackBack URL for this entry:
http://blogs.oracle.com/mte1521/mt-tb.cgi/2141

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

About This Entry

This page contains a single entry from the blog posted on February 17, 2007 7:40 PM.

The previous post in this blog was An Application Tuning Case Study: The Deadly Deadlock.

The next post in this blog is Best Practices For Custom Order Entry Workflow Design.

Many more can be found on the main index page or by looking through the archives.

Top Tags

Creative Commons License
This weblog is licensed under a Creative Commons License.
Powered by
Movable Type and Oracle