Or even here where the collations are different:

select *

from sys.objects

where name = ('sysrscols' collate French_CI_AS) collate French_CS_AS;

wow! 1% of respondants considered a cursor was the solution to a question on sequences

support for these data types was introduced in sql2005 - instead of keeping the data in the row, pointers to other pages are used to enable larger chunks of memory...

saying an array is '0' based does not really illustrate the situation.  The index is a position offset. So the first element is at the allocated address and the second...

Another QOTD where the explanation would only leave the inexperienced wondering...The correct response was to indicate the setting which would give an error but the explanation contradicts the answer...

What should we do when the answers are flawed like this?  I also went for 9 hours because I assumed that was the intended correct response...

Yes,  I had to try it out to prove to myself that "SELECT @sql" wasn't some underhand feature I didn't know about but of course I got the...

Thank you people - thought I'd lost the plot for a minute there.  Doesn't anyone review these questions before they are published?