Re: Not Exists joining 2 tables
- From: jhofmeyr@xxxxxxxxxxxxxx
- Date: Wed, 28 Nov 2007 03:40:09 -0800 (PST)
On Nov 28, 5:46 am, Ed Murphy <emurph...@xxxxxxxxxxxx> wrote:
creedp...@xxxxxxxxx wrote:
Consider this alternative and let me know if I screw this one up,
after all, it's getting late, and I'm still at work :) .....
SELECT company.code, company.name, company.type,
contacts.fullname
FROM company Left JOIN
contacts ON company.code = contacts.code
AND (company.type in ('C', 'R')) and (contacts.fullname =
'Accounting')
WHERE contacts.code IS NULL
order by company.code
I think this would work (except in the unlikely case that
contacts.code is nullable, in which case it might return
some data that it shouldn't). But NOT EXISTS has the strong
advantage of letting you say what you mean.
The last time I tried this (on a fairly complex query as well) on SQL
2005, the execution plan of using a NOT EXISTS and LEFT OUTER JOIN to
filter rows was identical. Could it be that the query optimiser
actually understands what we are trying to achieve and derives the
best method to do so regardless of syntax these days? More likely it
was simply a quirk of the query / tables / indexing I guess...
J
.
- References:
- Re: Not Exists joining 2 tables
- From: creedp . 71
- Re: Not Exists joining 2 tables
- From: Ed Murphy
- Re: Not Exists joining 2 tables
- Prev by Date: Re: Importing data into SQL Server 2005 via ODBC
- Next by Date: Re: Clustering, Security, Performance, Load Balance
- Previous by thread: Re: Not Exists joining 2 tables
- Index(es):
Relevant Pages
|
