I'm looking more for SSAS 2008 best practice design advice, rather than for an answer to a specific question (although I have a specifc set of examples).
First issue: Creating a non-additive measure group and an additive measure group. We have some fact data in our current cube that is additive, and some fact data that is non-additive; all stored in the same fact table. We do not currently
have measures implemented that reflect this aggregation distinction. Question: Is it considered good practice to segregate additive and non-additive fact data into a) different fact tables and/or b) different measure groups? My thought is
that it would be an acceptable design approach, but am looking for feedback.
Second issue: Non-additive fact data is only available at a non-leaf grain. The example here is that we have non-additive fact data which is only available for the 4th or 5th levels of our 6-level geography dimension. Our solution has been
to create a custom geography branch, which now essentially serves as our 'aggregation treatment' for non-additive fact data. I don't believe it's a good practice to have the geography dimension serve this function because we end up having to create a
custom geo member for each non-additive fact data element. Question: What is considered best practice
View Complete Post