Materialized views are a truly powerful feature of Oracle. Although materialized views are applicable only to certain usage scenarios, they can provide a real performance boost for specific situations without having to change any of the applications that are relying on your Oracle database.
In this module, you learned how to:
- Describe a materialized view and its uses
- Describe the parameters and what they mean in the
CREATE MATERIALIZED VIEW command
- Write SQL to create a materialized view that stores summary data
- Describe the conditions and types of indexing for materialized views
- Check the status of a materialized view and fix it
Descibe what conditions allow for query rewriting
- Describe the function of the
If you are using Oracle for a data warehouse or remote or distributed applications, materialized views may give you a performance gain with a minimum of effort.
The following terms were defined in this module:
- Bitmapped Index: Uses individual bits in an index entry to identify the value of an entry. A bitmapped index works best when there are a limited number of values for an index.
- Data Warehouse: A type of database that is used for analysis of data. The data warehouse frequently has a different type of structure a
star schema as opposed to a standard normalized schema and is also frequently separate from an organization's transaction database.
- ROWID: An internal value that uniquely identifies each individual row in an Oracle database.
In the next module, you will learn about index enhancements in Oracle.