× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. March 2004

Re: query optimizer revisited - this shouldn't be this hard!

Hi Rick -

ok, reasonable enough.  so I change the opnqryf and the index to match each
other better, while having the same results.

CREATE INDEX HISTRY4LA
    ON HISTRY4 (HPEROD, HITEM, LMRKTC)

and

OPNQRYF FILE((HISTRY4))
QRYSLT('HPEROD *EQ "06" *AND HITEM *NE 0 *AND LMRKTC *NE "00"')
KEYFLD((HPEROD) (HITEM) (LMRKTC))

I ran again, and it says it considered my index, but rejected it because of
reason 4.
  4 - The cost to use this access path, as determined by the optimizer, was
higher than the cost associated with the chosen access method.

Try the same thing but with OPTIMIZE(*FIRSTIO) as I suggested previously.

OPTIMIZE(*FIRSTIO) tells the optimizer that you want the first record as quickly as possible, so it is much less likely to build an access path itself.

--
Ken
http://www.ke9nr.net/
Opinions expressed are my own and do not necessarily represent the views of my employer or anyone in their right mind.


As an Amazon Associate we earn from qualifying purchases.

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

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.