• Subject: Query Optimizer
  • From: Pete Hall <pbhall@xxxxxxxxxx>
  • Date: Wed, 03 Nov 1999 19:11:42 -0600

Does anyone have a clue as to why the query optimizer would chose to build 
a temporary access path with a key that exactly matches the second of two 
logical files (no includes or omits)? The explanation says that "The cost 
to use this access path, as determined by the optimizer, was higher than 
the cost associated with the chosen access method" (which was to build a 
temporary index). Does the fact that this is a logical file (DDS) as 
opposed to and SQL index have any bearing on the matter? This is at V4R3, 
current on database PTFs.
Pete Hall
| 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

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].