Forum Discussion

wilson_smyth's avatar
wilson_smyth
Post Patron
7 years ago

Best design choice for multiple granularity

I have a data model which i need to report on at multiple granularities. Below is an example query that will populate the fact table with ID's from each dimension.     select o1.id, o2.id...
Need Help
wilson_smyth's avatar
wilson_smyth
Post Patron
7 years ago

Thansk for the reply.


Merging/appending is not the issue. obtaining the data is easy via merge/append or just modifying my source queries. Im asking about design practices, specifically:

 

- when there are many shared dimensions, is it better to have seperate fact tables at the desired granularity so that i dont have to deal with nulls when a row does not exist at a higher granularity

OR

should i have 1 single fact table, and wherever there are NULLS due to data not available at a lower granularity, populate it with the "unknown" value that i populate into the dimensions & deal with it in dax code.

 

kris999's avatar
kris999
Frequent Visitor
6 years ago

wilson_smyth 

 

I find myseflf regularly in the same sitiuation. Therefor the subject interests me greatly


What was your end conclusion on this subject?

Where you able to find more info?