The most likely suspect is a trigger on the table you're inserting into.

I totally missed that spurious semicolon in the subquery.

I was focused on the logic of the statement, and not a spurious typo.

This question TOTALLY FAILS to illustrate any point about...

The correct answer to this question is incorrect.

The keyword "NULL" represents the special value NULL.

In the context of (relational database) boolean logic, there are three possible values: TRUE, FALSE and...

In general, the number of bytes required to store a unicode character DEPENDS on the encoding.

Since we know SQL Server uses UCS-2 encoding, the most correct answer is 2...

So, what, we're going to hope that the single character to be stored isn't unicode?

Because with either char(1) and varchar(1), we're going to disallow a whole bunch of unicode characters...