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.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
Please contact support@xxxxxxxxxxxx for any subscription related
Help support midrange.com by shopping at amazon.com with our affiliate
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.