![materialize table materialize table](https://hasura.io/blog/content/images/downloaded_images/postgres-views-and-materialized-views-with-graphql-fd75680888b8/1-aaBWLnKdOp_6YPzltA21xA.png)
Materialized views allow you to replicate data based on column- and row-level subsetting, while multimaster replication requires replication of the entire table. This technology enables you to roll out a database infrastructure to hundreds or thousands of users. Parameters allow you to create custom data sets for individual users without changing the deployment template. You can then use deployment templates to quickly and easily deploy materialized view environments to support sales force automation and other mass deployment environments. Create a Mass Deployment Environmentĭeployment templates allow you to precreate a materialized view environment locally. These benefits, combined with mass deployment and data subsetting (both of which also reduce network loads), greatly enhance the performance and reliability of your replicated database. In addition to not requiring a dedicated network connection, replicating data with materialized views increases data availability by providing local access to the target data. Whereas multimaster replication requires constant communication over the network, materialized view replication requires only periodic refreshes. They have lower network requirements and dependencies than multimaster replication because of the point in time nature of materialized view replication. Materialized views are updated through an efficient batch process from a single master site or master materialized view site. Further, the ability of multimaster replication to provide real-time or near real-time replication may result in greater network traffic, and might require a dedicated network link. While multimaster replication also distributes a corporate database among multiple sites, the networking requirements for multimaster replication are greater than those for replicating with materialized views because of the transaction by transaction nature of multimaster replication. To decrease the amount of data that is replicated, a materialized view can be a subset of a master table or master materialized view. Through the use of multitier materialized views, you can create materialized views based on other materialized views, which enables you to distribute user load to an even greater extent because clients can access materialized view sites instead of master sites. Instead of the entire company accessing a single database server, user load is distributed across multiple database servers.
![materialize table materialize table](https://oracle-base.com/articles/misc/images/materialized-views/materialized-view.png)
If one of your goals is to reduce network loads, then you can use materialized views to distribute your corporate database to regional sites. You can use materialized views to achieve one or more of the following goals:
![materialize table materialize table](https://materialize.com/wp-content/uploads/2020/08/Purchase-1-1536x601.jpg)
If, however, no changes at all were made to the master since the last refresh of a materialized view, then the materialized view refresh should be very quick. Therefore, if any changes where made to the master since the last refresh, then a materialized view refresh takes some time to apply the changes to the materialized view. When a materialized view is fast refreshed, Oracle must examine all of the changes to the master table or master materialized view since the last refresh to see if any apply to the materialized view. Text description of the illustration rep81072.gif
![materialize table materialize table](https://media.geeksforgeeks.org/wp-content/uploads/20200527222256/Screenshot345.png)
Figure 3-1 Materialized View Connected to a Single Master Site The arrows in Figure 3-1 represent database links. Whereas in multimaster replication tables are continuously updated by other master sites, materialized views are updated from one or more masters through individual batch updates, known as a refreshes, from a single master site or master materialized view site, as illustrated in Figure 3-1. The master can be either a master table at a master site or a master materialized view at a materialized view site. Oracle9i Data Warehousing Guide to learn more about materialized views for data warehousingĪ materialized view is a replica of a target master from a single point in time.