When designing a table, it is essential to realise that there are real-world circumstances where NULL may be an important and meaningful representation of the data being modelled.

That's weird.  I'm doing GDPR at work and I clicked on the correct answer, but it marked me as wrong, while telling me that the correct answer was the one...

I'm a dev, not a DBA, and we're using Dapper.
https://github.com/StackExchange/Dapper

Yet another wrong QoTD.

Can I have my point(s) now please?

The MSDN article to which you link and which you cite in support of your (incorrect) answer states "Associates up to 128 bytes of binary information with the current session...

I went with this (the Stored Procedure is a WHILE loop that iterates over either 365 or 366 days.  @DateToInsert is the current date being processed; the other variables are...

Thanks but that doesn't solve the problem.  The table already has a MonthNumber column which corresponds exactly with the value of the month's date (e.g. January = 1, February =...

Good question, thanks.

Another borked QotD

I think you'll find that it's mulitplication and addition that are commutative.