When a user selects data from the view, only the result set is passed over the network—all of the joins and aggregations are performed on the server, not on the client. Then grant appropriate permissions on the views for the users and roles you want to be able to access the data.
Views can also be used to hide the real column names or underlying schema of your tables.
The proposed scheme is 100% consistent with the relational model, but rather different from the way updating works in SQL products today.The following Transact-SQL statement selects all the data for the view shown in Listing 9.1, sorting the result set on the Company Name column: statement wouldn't have to change. Company Name Views are created inside individual databases, however, views can reference tables and views in other databases or even on other servers (if the view is defined using distributed queries).The information about where the data in a view comes from and how it is pulled together from various tables is all encapsulated inside the view. Here are some general guidelines for creating views: Views are frequently used as security mechanisms to prevent users from having direct access to tables while still allowing them to work with data.To return the top 10 customers or the top 10% of customers, based on sales over the past year, SQL Server needs to sort customers by sales.So, a view that returns the top 100% by sales would essentially be a sorted view.
Search for updating view:
It's great to get the extra features, but it makes it harder to nail down exactly what you can and cannot do with views.