RE: Query Optimizer

["Ken Sims at SWS Nevada" <ken.sws@xxxxxxxxx>]

Hi Scott -

>Date: Thu, 4 Nov 1999 12:36:07 -0700 
>From: Scott Mildenberger <Smildenber@Washcorp.com>
>Subject: RE: Query Optimizer
>
>I'm not sure why the optimizer chose what it did, one guess might be that
>maybe the access path maintenance wasn't set to *immed so it wasn't current.
>But I do know one thing, if you create a logical file that can reuse an
>existing access path it is built almost immediately.  If the temporary
>access path that the optimizer built exactly matched the existing LF then it
>would have been built in a very short time.  I'm assuming since you asked
>the question that this temporary index took some time to build.  If that is
>the case then there must have been something different between the temporary
>index and the existing LF.  Not sure this helps but you may want to look at
>all the attributes of the existing LF.

The optimizer can be pretty *&%$ stupid at times.  There are situation when
I *know* that a certain logical would work just dandy, but the optimizer
builds a temporary index anyway.  Sometimes I could write, compile, and run
an RPG program to do the same thing in less time than it takes for the index
to build.  :(

The other problem is that the temporary index code is below the normal logical
file creation, so a temporary index will not share an existing logical file
access path.

Ken
Southern Wine and Spirits, Inc.

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---