This topic has certainly produced some interesting comments however I really can't disagree strongly enough with the "purist" mind frame that one solution, technique or algorithmic aim will solve all...

Well, I don't have 40 years... but I certainly agree with many of these points. Particularly those about documentation (or more accurately, the total lack of it) and error handling.

For those that care about the assumption of integer compared to a floating point column definition, try this:

DECLARE @LineItem TABLE
(
    LineItemKey INTEGER NOT NULL...

Part of the question is:

Responses that the calculation are incorrect, and even good ways...

While it's good that there are standards around SQL, otherwise we'd be living in a complete hell of vendor specific nonsense (much more than we are), there are two problems....

Strange... I was looking for the obvious answer that the data was missing a comma after the row Anderson.

Marvellous. I now feel a strange need to start putting my last name as NULL in all the tedious places that I'm required to enter personal details for no benefit...

When writing or reviewing code I prefer dark themes. Experience has shown that there's much less eye strain this way on an emissive screen and it's one of the first...