I'm running several calculations, stored within the cube attached to the measure groups, which use "prevmember" as a navigation hint, to take the predecessor within the same hierarchy.
[dim time].[booking period].prevmember,
When requesting multiple members on the granular level, for instance 40 products, and placing the calculation within the columns, performance slows down with factor 6 in comparison to using currentmember. As one would think stepping the hierarchy shouldn't
be so expensive I've tried different approaches.
Alternatives seem to be using "Scope" as well calculated dimension members. Could someone give me pros and cons or do you recommend something else?
We're Running SQL2005 SP2 enterprise
Business Intelligence professional
View Complete Post