Forum Discussion
Direct Query (multiple semantic models), multiple Date Table, and relationship
How do people do it in the industry?If you have dimension duplication caused by composite models then you pick the dimension from one of the models and remove it from all others. Unless your business scenario requires it you should only have one calendar dimension table in your combined data model.
How do people do it in the industry?If you have dimension duplication caused by composite models then you pick the dimension from one of the models and remove it from all others. Unless your business scenario requires it you should only have one calendar dimension table in your combined data model.
lbendlin Thank you very much! It's exactly what I mean, "dimension duplication caused by composite models". I didn't know the terms so I can't even search it.
So do you have any quick tips where I should place the "Organization-wide Date Table"? do people make one separate semantic model just for date dimension, or shall I keep my Date Table in the most important semantic model and link other models to that Date Table?
Thank you very much!
That's totally up to you. Doesn't seem to make a performance difference, at least not from my tests. YMMV.
