elvenmaiden
Programmer
Could anyone discuss the pros and cons of using a mart vs. a materilized view?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Marts vs. materialized views
- Thread starter elvenmaiden
- Start date
- Status
johnherman
MIS
The data mart will be more efficient since it can handle slowly changing dimensions and will use surrogate/synthetic keys for joins, which (when indexed) will perform faster than any natural keys available in the materialized view.
Materialized views can be useful when the end users are unsure of what they will want to do with the data. As the view, or materialized view, becomes stable and the users stop asking for changes, it would be appropriate to begin the design of a star schema for the data mart which would then be populated, validated, and followed by the retiring of the materialized view.
-------------------------
The trouble with doing something right the first time is that noboby appreciates how difficult it was.
- Steven Wright
Materialized views can be useful when the end users are unsure of what they will want to do with the data. As the view, or materialized view, becomes stable and the users stop asking for changes, it would be appropriate to begin the design of a star schema for the data mart which would then be populated, validated, and followed by the retiring of the materialized view.
-------------------------
The trouble with doing something right the first time is that noboby appreciates how difficult it was.
- Steven Wright
- Status