While I'm about to leave ASA 8.0.3 behind, I made some comparisons with ASA 220.127.116.1174 and SA 18.104.22.16866 and accidently used EXCEPT and INTERSECT on ASA 8.0.3.
I had strongly expected a syntax error as I was absolutely sure both set operators were introduced with ASA9 (and they are not at all documented with ASA 8), but they work.
Just couldn't believe it: Have I deliberately - but unfounded! - left out these handy operators all those years when working with ASA 8 (while using them on newer version)?
Or have I missed a relevant piece of information?
But wait and calm down, Volker - they seem to get accepted syntactically in ASA 8.0.3 but don't seem to work correctly, i.e. a
does return the same resultset as without the EXCEPT clause or with an INTERSECT clause.
So it seems I have not missed an important feature...
My pulse is still accelerating...
In version 8, EXCEPT would not have been recognized as a keyword. In your example, it would have been treated as an identifier, specifically an alias for table1. The line:
would have been treated as a Transact-SQL batch returning two results sets. If you execute it in DBISQLC and then enter "resume", you'll see the second result set.
answered 24 Sep '10, 13:32
Just to complete and answer the title question (whereas Bruce has answered the real question):
As already stated in my question - both set operators were introduced with ASA 9.0.
answered 24 Sep '10, 16:10