The view used to create the view left out the age column, therefore the insert statements that include age should fail.

I wonder if instead of using literal number 8000, you could limit the number of rows in the first CTE

to count the number of delimiters in the string, but adding...

You ABSOLUTELY do not want to use SELECT *.

That alone with cause all kinds of performance problems.  There are multiple articles explaining why.  You will have to generate the list...

Did you try putting db name master in single quotes?

Or, based on what I'm seeing in my database, the order of hierarchy is reversed, so it may be that the tables could be truncated in the order of

ORDER...

This has gotten way off topic and has become a rant on something not even related to SQL Server.

If you can't talk sense into him, find another company.

Also, if programmers were not allowed to write SQL code.

I hope that stripping whitespace at the expense of proper indenting to make the code readable (and thus more maintainable) is not what that guy did.

I hope you were not advising to turn the power throttling during low cpu usage back on. Keeping CPU at full power and ready to handle spike without having...

Also, to continue, there is another discussion that seems to expand on the OVER (ORDER BY ...) technique, adding that using function ROW_NUMBER on large tables can be counterproductive. ...

I just read the original article and wanted to add comment.

I believe if one wanted to "fix" the original SQL query

SELECT

Employee.EmpID,

Employee.EmpName,

...

CASE in WHERE clause might cause optimizer to ignore indexes and in some cases might cause RBAR processing and/or full table scans, such as calling functions in a WHERE clause.

...

Just need to avoid using a CASE statement in a WHERE clause (or ON condition).

SELECT ROW_NUMBER( ) OVER (ORDER BY

...