Hi All
I wanted to know if there is a reason or a situation, when one needs to snowflake instead of star.
Snowflaking looks like normalized operational design.
Please suggest.
Thanks
Dsedi
Snowflaking
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
There are reasons, but they should be rare. Allow me to quote from The Data Warehouse Lifecycle Toolkit by Kimball et al:
Then ask who's paying your salary?Generally snowflaking is not recommended in a data warehouse environment, Snowflaking almost always makes the user presentation more complex and more intricate. Database designers often like this intricacy, but users are often intimidated by the detail. Snowflaking also makes most forms of browsing among the dimensional attributes slower.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
I agree with Ray.. (and/or Mr. Kimball) I tend to avoid snowflake designs if at all possible. I've worked with a lot of architects for data warehouse designs and anytime I've seen snowflake designs implemented it lead to problems as soon as the end users in the BI tool started accessing the data.
If your "end users" are all database / BI consultants that are pre-building the entire BI front-end for the business users, then you can get away with using snowflakes (though there is a performance penalty of course).
If your "end users" are all database / BI consultants that are pre-building the entire BI front-end for the business users, then you can get away with using snowflakes (though there is a performance penalty of course).