RE: SQL Syntax

[Alexei Pytel <pytel@xxxxxxxxxx>]

Perhaps we are talking about different things...
You mention "logs" and probably refer to optimizer messages sent to joblog
in STRDBG mode.
What I was talking are DB monitor (which sends very detailed - and
admittedly cryptic - records to a database file) and Visual Explain
(Operations Navigator plug-in which interprets these records).
Visual Explain is a GUI interface and it shows a nice flow-chart of a
query, which steps were taken, in what sequence, how many recorsd were
selected at each step and what was the cost of the step in terms of how
many records were processed, how many I/Os were made, etc. etc.
Exactly your question - why one statement is more expensive then another.
Usually looks pretty understandable to me ...

    Alexei Pytel
always speaking for myself




                      "Joe Pluta"
                      <joepluta@PlutaBro        To:       
<midrange-l@midrange.com>
                      thers.com>                cc:
                      Sent by:                  Subject:  RE: SQL Syntax
                      midrange-l-admin@m
                      idrange.com


                      10/29/2002 02:55
                      PM
                      Please respond to
                      midrange-l





> From: Alexei Pytel
>
> There is no black magic.
> Run DB monitor for your query and use SQL Visual Explain from Operations
> Navigator.
> It will show you how your query was performed in more detail than you
want

See my post on this.  Sort of fittingly with the rest of this conversation,
Visual Explain shows a lot of data on the SQL statement, but very little
real information.  Nothing in all those wonderfully verbose logs indicates
WHY one statement took 50 times longer than the other.  Sure, there are
differences, but nothing meaningful, at least to me.  Perhaps I'm an idiot,
but I challenge anyone to read my logs and decipher the "why" from the
data.

As I said in a different post, there's data, and then there's information.

Joe

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.