This question came from a previous post / my solution:
Adding a field somehow affects view results
IMO deserves its own post. Using SQL Server 2008 R2.
Why do I need to update views after adding a column to the table referenced in the view? Although this is not necessary to answer this post / question, the script / behavior for my particular scenario explain the message above.
I am not a big fan of looks. Very rarely, I create them to be honest, I work with code that I did not originally write. Let's say you have 70 views that you did not initially write, so you have no idea which ones need to be updated each time you add a database column. I should be able to add that ever column that there is ever a table at any time, without any influence frankly. A business unit may raise a request for any changes that may require any number of added fields at any time.
Is there really another approach to this?
source share