Designing of Dimension.
-
Friday, January 18, 2013 2:33 PM
Hi all,
I am new to DWH design.
I need one help regarding the designing of dimension.
Look-up shipping method table contains the below data
ID
Name
Changed Name
1
2-3 days
2\3 Days
2
3-5 days
Order dimension Contains the below data
SO no
So date
name
SO1
2013-01-17
2-3 days
SO2
2013-01-17
3-5 days
SO3
2013-01-18
2\3 Days
Here, After inserting of SO2, name of the shipping method may got changed. For this type of situations will store the id\id and name\ name only.
Main concern here is, while storing look-up tables information in dimensions whether will store the id or name or id and name of look-up table in the dimension and then map this look-up in fact.
Let me know if you need any additional information on this.
- Edited by AV9999 Friday, January 18, 2013 2:59 PM Changed title
All Replies
-
Saturday, January 19, 2013 6:29 PM
And Order would be a fact, not a dimension. And you should store references to other rows using a foreign key, just like in a transactional design. If use a surrogate key on your dimension rows, then that's what should appear in your fact table.
There are times when you copy a non-key attribute of a dimension down to a fact table for convenience or performance, but this should be the exception rather than the rule, and the dimension key should also be there.
See, eg
http://www.amazon.com/The-Data-Warehouse-Toolkit-Dimensional/dp/0471200247
David
David http://blogs.msdn.com/b/dbrowne/
- Marked As Answer by Eileen ZhaoMicrosoft Contingent Staff, Moderator Thursday, January 24, 2013 1:49 AM
-
Monday, January 21, 2013 4:02 PM
Hi
Easy way to do New Dimension Using the Dimension Wizard,To know pls click on :
http://msdn.microsoft.com/en-us/library/ms365388(v=sql.105).aspx
Ahsan Kabir Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread. http://www.aktechforum.blogspot.com/
.png)
