Efficiently updating materialized views

1 Introduction In a relational database system, a database may be composed of both base and derived relations.

A de- This work was supported in part by scholarship No.

We propose a method in which all database updates to base relations are first filtered to remove from consideration those that cannot possibly affect the view.

The conditions given for the detection of updates of this type, called irrelevant updates, are necessary and sufficient and are independent of the database state.

Let’s see that: With the standard edition of SQL Server it does not even use “materialized” data by default.

efficiently updating materialized views-65efficiently updating materialized views-81efficiently updating materialized views-77efficiently updating materialized views-68

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 .This chapter includes the following sections: The database maintains data in materialized views by refreshing them after changes to the base tables.Performing a refresh operation requires temporary space to rebuild the indexes and can require additional space for performing the refresh operation itself.Refreshing a materialized view automatically updates all of its indexes.In the case of full refresh, this requires temporary sort space to rebuild all indexes during refresh.

Leave a Reply