A materialized view is a database object containing the results of a SQL query. The concept is also known as “Query rewrite”. It might be a local copy of remotely located data, a subset of a table’s rows and/or columns, a join result, or a summary created using an aggregate function.
When a materialized view is executed, the SQL query is persisted in storage, enabling a fast query response.
So you see, the terms are coming back. The Oracle Database first implemented ==materialized== ==view==s in version 8i (1998). They were added later by Postgres and SQLServer.
# Oracle Syntax
# Creating a Materialized View
# Refreshing Materialized Views
If a materialized view is set to refresh on commit, manual refreshes are typically unnecessary, except when a rebuild is required. Remember, refreshing on commit can be resource-intensive for volatile base tables. Fast refreshes are generally preferable.
For on-demand refreshes, either manual refresh or inclusion in a refresh group is possible.
The code below demonstrates creating a refresh group scheduled to refresh every minute, and adding a materialized view to it.
Origin: The first technique I used in the Oracle database in 2008.
References: One Big Table (OBT) or Snapshotting or Materialized Views