Database ease of updating

This causes the advantages of views to become muddled and misunderstood.As you read this article you will find that views are very useful when implemented wisely, but can be an administrative burden if implemented without planning.Additionally, inserting data is prohibited for the following types of views: It is also possible to insert or update data through a view such that the data is no longer accessible via that view, unless the WITH CHECK OPTION has been specified.Almost any SQL that can be issued natively can be coded into a view; there are exceptions, however.For example, the UNION operator can not be used in a view and you cannot create a trigger on a view.All of the basic DDL statements can be used to create and manage views including CREATE, DROP, and ALTER.Views should be created only when they achieve a specific, reasonable goal.

This section provides the rules of thumb for when it is wise to create views.

Guidelines such as these should be instituted within your organization to reduce the amount of time and effort required to implement effective views.

The following rules will ensure that views are created in a responsible and useful manner at your shop.

There is no adequate rationale for enforcing a strict rule of one—view per base table for SQL Server application systems.

In fact, the evidence supports not using views in this manner.

Leave a Reply