Oracle Materialized View Editor
Use the Oracle Materialized View Editor to create or edit materialized views.
A materialized view, which is a view that stores the result set of a query against any number of other materialized views, views, and tables. Materialized views can be used to improve the performance of queries. To the database user, a materialized view looks like a real table with a set of named columns and rows of data. However, a materialized view is not a permanently stored set of data values. The rows and columns of data visible through the materialized view are the result of the database query that defines the materialized view.
You can use materialized views to:
- Create a customized presentation of the data stored in a database.
- Restrict access to data, allowing different users access to only certain rows or columns of a materialized view.
- Simplify database access by creating customized structures tailored to the needs of individual users. A user can write a simple query on a materialized view rather than a complex query on the actual database tables.
Materialized views are supported in the following features:
- Forward Engineering
-
When you forward-engineer your data model to generate a database, the SQL code to define the materialized view is generated, and it is stored in the database.
- Reverse Engineering
-
When you reverse-engineer an existing database that includes one or more materialized views, each materialized view is imported, the syntax is parsed, and where possible the relationships to the tables referenced by the materialized view are created.
- Complete Compare
-
When you use complete compare and update a materialized view either in the model or in the database, you can keep the model materialized view specification in sync with the database table specification.
When you add a materialized view to a model, it is represented as a box with rounded corners. A relationship between a table and a materialized view indicates that the materialized view table references one or more of the columns from that table.
The following properties are applicable to an Oracle Materialized View object.
Tab |
Section |
Property |
Description |
Additional Information |
Name |
Specifies the physical name of the materialized view | |||
Owner | Specifies the database owner | |||
Generate | Specifies whether a SQL statement for the materialized view is generated during forward engineering | |||
General | Storage Type | Data Storage Type | Specifies the storage characteristics of the materialized view |
Regular: Indicates that the materialized view is a regular materialized view Organized: Indicates that the materialized view rows use an organization type to store rows Cluster: Indicates that the materialized view is a part of the specified cluster |
Data Organization Type | Specifies the organization type for Organized data storage and the order in which the data rows of the materialized view are stored |
Available only when Data Storage Type is set to Organized Heap: Indicates that the materialized view is heap-organized and rows do not follow any specific order Index: Indicates that the materialized view is index-organized and rows are held in an index defined on the primary key |
||
Deferred Segment | Specifies the point at which the database creates materialized view segments |
Immediate: Indicates that a segment is created along with the materialized view Deferred: Indicates that a segment is created only when the first row of data is inserted into the materialized view |
||
Cluster | Oracle Cluster | Specifies the cluster to be used | Available only when Data Storage Type is set to Cluster | |
Clustering Columns | Column | Specifies the materialized view columns that correspond to the specified cluster's columns | Available only when Data Storage Type is set to Cluster | |
Compression |
Compression |
Specifies the compression technique to be used to compress data segments | Available only when Data Storage Type is set to Regular or Organized (and Data Organization Type is set to Heap or left blank) | |
Index Organization |
Percent Threshold |
Specifies the space blocked in the index block | Available only when the Data Storage Type is set to Organized and Data Organization Type is set to Index | |
Prefix Compression |
Specifies whether prefix compression is enabled | |||
Prefix Compression Value | Specifies the number of prefix columns to compress | |||
Index Overflow | Specifies whether the row exceeding the Percent Threshold are placed in a data segment | |||
Including Column | Specifies the column at which a row is divided into index and overflow parts | |||
Refresh Properties | Refresh State | Specifies whether the materialized view is configured to refresh | ||
Refresh On What | Specifies the event that triggers the refresh |
Demand: Indicates that the database refreshes the materialized view only when a refresh is demanded manually Commit: Indicates that the database refreshes the materialized view whenever a transaction on the master table is committed Statement: Indicates that the database refreshes the materialized view whenever a DML operation is performed on the master table |
||
Refresh Type | Specifies the refresh method |
Fast: Indicates that the refresh operation is performed based on the changes that occur to the master table Complete: Indicates that the refresh operation is performed by executing the query that defines the materialized view Force: Indicates that the refresh operation is performed based on the method (Fast or Complete) that is possible |
||
Refresh Start Date | Specifies the datetime expression for the first automatic refresh operation | |||
Refresh Next Date | Specifies the datetime expression to calculate the interval between automatic refresh operations | |||
Refresh With Key | Specifies the type of key to be used |
Primary Key: Indicates that the materialized view is eligible for fast refresh even with master table reorganization Row Id: Indicates that the materialized view is not eligible for fast refresh after a master table reorganization until a complete refresh has been performed |
||
Refresh Local Rollback Seg State | Specifies the remote rollback segment to be used for the local refresh group that contains the materialized view |
Default: Indicates that the database automatically selects a rollback segment to use Specified: Indicates that the database uses a specified rollback segment |
||
Refresh Local Rollback Seg Reference | Specifies the rollback segment to be used | Available only when the Refresh Local Rollback Seg State is set to Specified | ||
Refresh Master Rollback Seg State | Specifies the remote rollback segment to be used at the remote master site for an individual materialized view | Default: Indicates that the database automatically selects a rollback segment to use Specified: Indicates that the database uses a specified rollback segment |
||
Refresh Master Rollback Seg Reference | Specifies the rollback segment to be used | Available only when the Refresh Master Rollback Seg State is set to Specified | ||
Using Constraint Type | Specifies the constraint type to be used by the database to find more rewrite options during the refresh operation | |||
Storage | Storage | Name | Specifies the physical storage object for the materialized view | |
Index Overflow Storage | Name | Specifies the overflow storage object for an index-organized materialized view | Available only when the Data Storage Type is set to Organized and Data Organization Type is set to Index | |
Other Options |
Object Properties | Of Type | Specifies the type object for an object materialized view | |
Other Options | Prebuilt Table | Specifies whether an existing table is registered as a preinitialized materialized view | ||
Reduced Precision | Specifies whether loos of precision is allowed if the precision of the table or materialized view columns do not exactly match the precision returned by subquery | |||
Default Collation | Specifies the default collation | |||
Cache | Specifies how data blocks are stored in the buffer cache |
No Cache: Indicates that the blocks fetched for a table are placed at the least recently used end of the least recently used (LRU) list in the buffer cache when a full table scan is performed Cache: Indicates that the blocks fetched for a table are placed at the most recently used end of the LRU list in the buffer cache when a full table scan is performed |
||
Use Parallel | Specifies whether parallel operations are supported for the materialized view | |||
Parallel | Specifies the degree of parallelism (the number of parallel threads) | |||
Build Clause | Specifies when the materialized view is populated |
Immediate: Indicates that the materialized view is populated immediately on creation Deferred: Indicates that the materialized view is populated by the next REFRESH operation |
||
Use Index | Specifies whether a default index is used to maintain materialized view data |
Use Default Index: Indicates that a default index is used speed up incremental refresh of the materialized view Use No Index: Indicates that a default index is not created |
||
Index | Specifies the default index name | Available only when Use Index is set to Use Default Index | ||
Computation Query State | Specifies whether a real-time materialized view is created so that up-to-date is available for queries even when the materialized view is not in sync with the base table |
|
||
Query Rewrite State | Specifies whether the materialized view is eligible to be used for query rewrite |
The Oracle Materialized View Editor also includes the following tabs:
-
Select Lets you specify the tables, views, or materialized views to use to define the materialized view and create aliases and expressions.
-
From Lets you specify the tables, views, and materialized views that you want to participate in the materialzied view.
-
Where Lets you enter text to define a WHERE clause.
-
User Defined SQL Lets you view and change a user-provided DDL statement.
-
SQL Lets you view the SQL code used during Forward Engineering.
-
Style Lets you work with style sheets, which are used to format the font and other graphical themes used in the display of the materialized view.
-
Icon Lets you specify the icon style to use for the materialized view.
-
Alias Lets you add, modify, or delete synonyms for the materialized view.
-
Comment Lets you enter any comments that you want to associate with the materialized view.
-
Object Creation Order Lets you specify the order of DDL generation.
-
UDP Lets you enter user-defined property values for a materialized view.
-
History Lets you view the history details for the materialized view.
-
Notes Lets you view materialized view history information and view or edit user notes.
-
Extended Notes Lets you edit user notes or transfer notes to the Notes tab.
Copyright © 2025 Quest Software, Inc. |