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



<snip>
Also, 600,000 records might simply be too much data. Sending all that
across the network could be what's slow.
</snip>

"Also" is the thing that is wrong. That IS what I am saying. Not only
are you sending all those records down to the client so it can then decide
which rows really matter, but you're making the SQL engine on that client
do that work. You should really find out a way to get the 'where' to
execute on the server. See my previous suggestions.


Rob Berendt

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.