• Calling a column ID and then putting duplicate values in it is just evil. No raise for the developer who wrote this, and a warning that (s)he'll be fired if it happens again.

    And not noticing it while working out the result of a QotD in my head is just stupid *facepalm*. No raise for me either.

    I do not really like what currently appears to be in fashion here, to write what appears to be a question about a SQL feature, but that actually tests our ability to detect sneaky issues that are hidden in the question and/or code. Yes, I know that being made responsible for existing code often is the same. I don't mind such questions every now and then. But I have this feeling (not based on any actual counting) that there are a bit too many of them lately.


    Hugo Kornelis, SQL Server/Data Platform MVP (2006-2016)
    Visit my SQL Server blog: https://sqlserverfast.com/blog/
    SQL Server Execution Plan Reference: https://sqlserverfast.com/epr/