Efficiently updating materialized views
1 Introduction In a relational database system, a database may be composed of both base and derived relations.
Therefore, if you defer refreshing your materialized views, you can either rely on your chosen rewrite integrity level to determine whether or not a stale materialized view can be used for query rewrite, or you can temporarily disable query rewrite with an .
Let’s see that: With the standard edition of SQL Server it does not even use “materialized” data by default.
If you want to force SQL to use the view data, you have to use (noexpand) hint.
There are two incremental refresh methods, known as log-based refresh and partition change tracking (PCT) refresh. Users can perform a complete refresh at any time after the materialized view is created.
The complete refresh involves executing the query that defines the materialized view.