I can't exactly answer your question because I don't have a copy of SQL...

That's not quite true. If you considered the...

To be fair, even if you saw the "Possible Error" in the INSERT (if you didn't know this was a SQL 2008 feature, like me) or if you ran it...

Hah, should have known Hugo would come explain everything properly - ignore my posts, concentrate on his 🙂

BrainDonor (4/13/2010)

---

It could have possibly have been phrased slightly better ("The fixed value NULL", or something like that), but it is correct. NULL does not equal NULL. Try comparing two...

Sorry, but within the context of Microsoft terminology, this is simply wrong.

Within the context of SQL Server documentation, "UNKNOWN" (all uppercase) is used exclusively as a Boolean result in SQL...

While the intent of the question is clear, there is currently some question as to the accuracy of the selected answer:

http://www.schneier.com/blog/archives/2009/07/another_new_aes.html

(I got the answer "right", not looking for my point...

Hmm, I was more bothered by the fact that NOT IN() is assumed to NOT be SARGable... In SQL 2000 this was always true when there was more than one...

Registry Access. Haven't figured out an efficient and sensible way to do it in SQL Server 2005 without using the CLR.

vkirkpat (12/2/2009)

---

But, the update DOES change the value, right? Even though it may be the same value, it does get updated. It's not like SQL Server says to itself, hey,...

A trickier variation could be the same question, without the "Insert" statement.

Even though there are no rows being updated in that variant, the trigger still finds that the column was...

To each his own, I guess!

To me, your "fix" makes it even harder to read (keeping a joined table on the same line as the first table? eek!) - but...

mohd.nizamuddin (9/30/2009)

---

David Walker-278941 (9/23/2009)

For table alises, programmers seem to get the idea that they are a required part of the syntax. In fact, for many readers, having to read...

Ah but if...

I considered trying to say that, but couldn't figure out how to do so as clearly as @sknox just did :-).