[thelist] Weird SQL problem with INTERSECT and UNION

ted serbinski tss24 at cornell.edu
Wed Apr 2 02:36:16 CST 2003

> However, if I change UNION to INTERSECT, I get an
> error near INTERSECT it says.

Think I figured out my own question. Seems like MS SQL does not support
INTERSECT, which is quite odd. Also, I figured out if I combine my queries
on the cost, and just AND the costs, instead of using INTERSECT, it works
great and the queries are much more simpler.

Still odd that MS SQL does not support INTERSECT. Is there any work arounds
for this or hacks to emulate it?


More information about the thelist mailing list