|
|
Posted by Gert-Jan Strik on 09/27/77 11:16
An indexed view is updated within the transaction that modifies the
relevant base table(s). In other words, the indexed view is updated
immediately.
So yes, the performance of inserts/updates/deletes will be influenced.
If it is a narrow view (few columns with few bytes), then the
performance hit would be comparable with the addition of a 'regular'
index to the base table.
HTH,
Gert-Jan
teddysnips@hotmail.com wrote:
>
> This from a SQL Server manual:
>
> "Complex queries, however, such as those in decision support systems,
> can reference large numbers of rows in base tables and aggregate large
> amounts of information into relatively concise aggregates (such as sums
> or averages). SQL Server 2000 supports creating a clustered index on a
> view that implements such a complex
> query. When the CREATE INDEX statement is executed, the result set of
> the view SELECT is stored permanently in the database. Future SQL
> statements that reference the view will have substantially better
> response times. Modifications to the base data are automatically
> reflected in the view."
>
> My question arises from the last sentence. At what point are the views
> updated with the new data? If I am running a transaction that updates
> some dependent tables, is there a performance impact while the indexed
> views are updated?
>
> Jess Askin.
Navigation:
[Reply to this message]
|