Sql server updating data in a view
Frequently occurring aggregations and joins are the best candidates for indexed views.
Whether or not a query is asked frequently, it may be a candidate for an indexed view if it takes significant time to answer, and the value of getting the answer quickly is high.
Any computations such as joins or aggregations are done during query execution for each query referencing the view1.
After a unique clustered index is created on the view, the view's result set is materialized immediately and persisted in physical storage in the database, saving the overhead of performing this costly operation at execution time.
Indexed views can increase query performance in the following ways: The graph demonstrates the typical performance increases that can be achieved when the query optimizer uses an indexed view.Adding indexes to the schema increases the overhead on the database because the indexes will require on-going maintenance.Careful consideration should be given to finding the right balance of indexes and maintenance overhead.This document describes the improved indexed views capability of SQL Server 2005 Enterprise Edition.Indexed views are explained and specific scenarios in which they may provide performance improvements are discussed. Benefits of Using Indexed Views What's new for Indexed Views in SQL Server 2005?