Re: Query tuning exercise: what to look for in a 10053 trace

I'd stick Cary's book in the D category, and suggest that it has one
advantage over OWI (which is an excellent book as well). That is that OOP as
well as dealing with profiling elapsed time also deals with whether you even
have a problem in the first place. OWI has an implicit assumption that there
is a problem worth looking at. As Gaja has pointed out oftentimes we can
dive right in with DUC when we don't need to. This which he
labelled Compulsive Tuning disorder is I believe the first of a new class of
conditions to which DBAs are susceptible. as well as OCD there is

RPI (Repetitive Patching Illusion - whereby patches are applied to patches
to patches in the hope of attaining system stability)
CUD (Compulsive Upgrade Disorder - the irrational belief that an upgrade
will clearly related to both CTD and RPI)

I'm sure there are others waiting to be identified


On 7/26/06, Dennis Williams <oracledba.williams@xxxxxxxxx> wrote: 

 Bernard,

Over the years I've come to appreciate someone who can summarize a complex
topic in a few succinct statements. Just to clarify for the rest of us,
please confirm that you are referring to:

  -  Oracle Wait Interface: A practical Guide to Performance Diagnostics
and Tuning (Osborne Oracle Press Series) by Richmond Shee, Kirtikumar
Deshpande, and K. Gopalakrishnan
  -  Cost-Based Oracle Fundamentals by Jonathan Lewis (I didn't know this
was out).
  -  SQL Tuning by Dan Tow

My only quibble is that there needs to be a place in your pantheon for
  -  Optimizing Oracle Performance by Cary Millsap and Jeff Holt.
I'm not sure what that does for your letter arrangement. Of course, since
the topic is SQL statement tuning, you could argue that Cary looks more
broadly to the application performance, rather than focusing on a specific
SQL statement.

Dennis Williams


 On 7/26/06, Bernard Polarski < bpolarsk@xxxxxxxxx> wrote:
>
>   Here we find again the holy trinity : DUC
>
>    Diagnose-Understand-Cure
>
> D : Why is my DB so slow --> Oracle wait interface (Oracle press)
> U : Why the CBO is doing that --> Cost based optimisation (JL)
> C : What should I do now --> Dan Tow, SQL tuning (Oreilly)
>
>



--
Niall Litchfield
Oracle DBA
http://www.orawin.info

Other related posts: