As more or less already said, however technically a 'smart' solution, the fact that this is the chosen way reveals that sourcecontrol and auditing of changes is hardly done in...

Creative statement good for braintraining but with a high theoretical fineness.

Not any SQL developer with some common sense would name a table [where] nor would invent the alias [flag ='y'...

Good brain training but are the restrictions as mentioned realistic? Which company would definitely not want to use a temp table or table variable?

Good article, by coincidence I wrote a script recently that generates three triggers for every table in a database for tracking change history of tablecontents into one single _Changehistory table...

It seems more logic to use a table-valued User Defined Function. This is what you would call a 'real' parameterized view, except for that it is technically not a view.

...