How can Oracle Materialized Views be used to speed up data
warehouse queries?
Answers were Sorted based on User's Feedback
Answer / sabeena
A materialized view is a database object that contains the
results of a query. They are local copies of data located
remotely, or are used to create summary tables based on
aggregations of a table's data. Materialized views, which
store data based on remote tables are also, know as
snapshots.
A materialized view can query tables, views, and other
materialized views. Collectively these are called master
tables (a replication term) or detail tables (a data
warehouse term).
For data warehousing purposes, the materialized views
commonly created are aggregate views, single-table
aggregate views, and join views.
| Is This Answer Correct ? | 7 Yes | 0 No |
Answer / mallika
In data warehouses, you can use materialized views to
precompute and store aggregated data such as the sum of
sales.
Materialized views are often referred to as summaries,
because they store summarized data. They can also be used
to precompute joins with or without aggregations.
A materialized view eliminates the overhead associated with
expensive joins and aggregations for a large or important
class of queries
| Is This Answer Correct ? | 4 Yes | 0 No |
Answer / svs rajesh
In oracle materialized view carry the carry with them so it
is easy 7 faster to retrieve the data for reporting instead
of goin to the actual database these provide the faster
retrieval of data.
| Is This Answer Correct ? | 6 Yes | 3 No |
What is meant by metadata in context of a data warehouse?
What is a Decision Tree Algorithm?
What is Sequence clustering algorithm?
Is there any difference in testing database and data ware housing?
I need a good brd and uc template?
What is data stream and data adaopter?
Explain the versions of reportnet?
What is the difference between static cache and dynamic cache?
what is parallelism?
In microstrategy, how can we direct the sql generated to use a specifc table?
Explain what is the difference between olap and datawarehosue?
Suppose we have some 10,000 odd records in source system and when load them into target.how do we ensure that all 10,000 records that are loaded to target doesnt contain any garbage values?