× 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.



On 2011-05-30 06:15, Jerry C. Adams wrote:
I never done the tests such as those done by Joe and Chuck. But a year or
so back I needed to write an order inquiry. For the most part I used SQL
Selects, and it worked reasonably well (i.e., sub-second response). Part of
the inquiry, though, was to potentially (if the user selected it) display
the details for a billed order in the history. Maybe I was just
inefficient, but that puppy took forever (i.e.,> 15 minutes) to return the
records I needed. The history details was around 1,000,000 records at the
time (and growing). I changed it to RLA, and got back the sub-second
response. The index used for the RLA, which was equivalent to the SELECT,
existed before I started writing the program.

My experience has been that if an appropriate index exists, performance knocks your socks off. If not, well, it doesn't. SQL does not like legacy indexes with include/exclude definitions either, so those won't do you any good. Index advisor is your friend...


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.