Should fact tables be in 3NF ?
3 posters
Page 1 of 1
Should fact tables be in 3NF ?
Hi all,
Here is a sentence from page 236 of The Data Warehouse Lifecycle Toolkit book. "Fact tables are typically normalized to 3NF in a dimensional model because the related context is removed to dimension tables". My question is if this is a design principle or a best practice.
Suppose that I have a fact table (Card no, Customer ID, Branch ID, Date, Amount) where Customer ID and Branch ID are functionally dependent to Card no and this fact table is not in 3NF. Is this a wrong design?
And if I remove Customer ID and Branch ID from fact table and put them as attributes of Card Dimension it would lead to a snowflake schema which we all know about issues like bad performance. Any Suggestions?
Regards,
Mehdi
Here is a sentence from page 236 of The Data Warehouse Lifecycle Toolkit book. "Fact tables are typically normalized to 3NF in a dimensional model because the related context is removed to dimension tables". My question is if this is a design principle or a best practice.
Suppose that I have a fact table (Card no, Customer ID, Branch ID, Date, Amount) where Customer ID and Branch ID are functionally dependent to Card no and this fact table is not in 3NF. Is this a wrong design?
And if I remove Customer ID and Branch ID from fact table and put them as attributes of Card Dimension it would lead to a snowflake schema which we all know about issues like bad performance. Any Suggestions?
Regards,
Mehdi
mehdigarakani- Posts : 2
Join date : 2012-05-06
Re: Should fact tables be in 3NF ?
Take a pen and draw a line through that sentence. Ignore it. Normal forms have no meaning in a dimensional model. He just mentioned it in passing for those who worry about stuff like that. But, unless you are normalizing your model, normal forms don't matter.
Re: Should fact tables be in 3NF ?
I think it means that nothing should be denormalized to the fact table.
Jeff Smith- Posts : 471
Join date : 2009-02-03
Similar topics
» Modelling question - Multiple fact tables with one to many relationships and querying from many fact tables
» Storing Date Keys in dimension tables versus fact tables
» Cost plans for projects - One fact table or several fact tables?
» Multiple Fact Tables vs. Consolidated Fact Table
» Number of Columns in Fact Tables vs. Dimension Tables
» Storing Date Keys in dimension tables versus fact tables
» Cost plans for projects - One fact table or several fact tables?
» Multiple Fact Tables vs. Consolidated Fact Table
» Number of Columns in Fact Tables vs. Dimension Tables
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum