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



Michael_Schutte@xxxxxxxxxxxx wrote:
I've never seen this brought up before so I thought I'll put this out
there. I can explain why but maybe someone else could. I've found that if
you join tables together that it's better that you put your where clause in
the join instead of the "where". Also putting the smaller table first
seems to help.
It's interesting, but from what I remember from people who probably have forgotten more about SQL than I know (people like Birgitta), the position of the where doesn't really matter on a JOIN, it all gets parsed down to the same code. However, the ordering of the tables can have significant impact, especially if you have additional filtering criteria. Which makes sense; if you have a file with order numbers to process, you don't read every record in the order file and chain to the list of orders to see if you should process it; you read the orders to process and chain to the order file.

Joe

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.