Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
coolerbob
Aged Yak Warrior
841 Posts |
 Posted - 2006-06-20 : 17:35:15
|
| There's one thing I'm not entirely clear on.Take the DimCustomer table in AdventureWorksDW.Say I want to monitor, not the sales to the customer, but rather I want to report on the change of their demographics and the resulting trends.That way I can say that last month I had 10 customers that earned more than 40K and this month I have 15.Now, the Dimention table only gives me current data. Would I have to have a fact table? That seems an overkill. The amount of repeadted data in there would be emmense.What concept am I not grasping? |
|
|
mwjdavidson
Aged Yak Warrior
735 Posts |
Posted - 2006-06-21 : 06:34:44
|
| Have at look at this article from 'Intelligent Enterprise Magazine': [url]http://www.intelligententerprise.com/020812/513warehouse1_2.jhtml[/url]. If the customer dimension is currently defined as a Type I (overwrite when attributes change), the shift to Type II will add a bit of complexity.Mark |
 |
|
|
coolerbob
Aged Yak Warrior
841 Posts |
Posted - 2006-06-21 : 10:24:26
|
| Fantastic link! That's exactly waht I'm after. Thanks Mark! |
|
|
|
mwjdavidson
Aged Yak Warrior
735 Posts |
Posted - 2006-06-21 : 10:50:14
|
| No worries - glad it was helpful! I came across it via [url]www.ralphkimball.com[/url] which is a great source of dimensional DW design tips and articles.Mark |
|
|
|
|
|
|
Fact and Dimension tables