I've seen NOT EXISTS and JOINS suggested. My opinion is that a NOT EXSISTS will perform the best for you. If you don't actually need a value from the child table, a join brings the possibility of a higher performance hit vs. the NOT EXISTS, which is accurately telling the optimizer that you don't want anything from the secondary table except to know if a record exists there.

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