Posted by James Foreman on 09/21/06 13:33

Thanks. From looking around a bit more on this group, INTERSECT &
EXCEPT are implemented in SQL Server 2005, but not in 2000. What
you've said is fine where there's a primary key available, but we've
had situations where that isn't the case and EXCEPT has been an easier
way to deal with this (eg you get given a lot of customer address data
that nobody has bothered to form a key on, and you only want to read in
rows you haven't already got. You *can* do it by comparing columns,
but once you have lots of columns to compare the code gets rather
ugly).

Plus I find EXCEPT easier to read, but that's more personal preference
than a good reason...

James

• Next in forum: Re: Question on System and Data Restore
• Prev in forum: Dyamic view/function based on table data (?)
• Thread view: Re: UNION / INTERSECT / EXCEPT in SQL Server 2000

[Reply to this message]