many-to-many dimensions should cause storage engine filtering on the data measure group - by GregGalloway

Status : 


Sign in
to vote
ID 636981 Comments
Status Active Workarounds
Type Suggestion Repros 0
Opened 1/19/2011 3:58:08 PM
Access Restriction Public


If you have a many-to-many dimension A with a common dimension B, the storage engine will have to request totals for EVERY member of dimension B from the data measure group when resolving this many-to-many dimension.

It would be VERY nice for performance if, after finding the members of dimension B that exist in your current slice in the intermediate measure group, you could have the storage engine only pull totals for just those members of dimension B from the data measure group.

My specific use case is this... I have a m2m Date and Date Calculations dimension so that a table can drive which days are in YTD 1/19/2011. But these m2m dimensions cause every date partition from the data measure group to be hit even if only recent date partitions are needed for my query.

In an email with Akshai today, he suggested this might be a nice enhancement, if that lends any weight.
Sign in to post a comment.
Posted by Philippe NGO on 3/27/2017 at 6:15 AM
Any news on this bug? Or a way to bypass it ?

It is really a blocker as it makes the many to many useless for very large cube.
Posted by James Stange, Jr on 12/12/2014 at 8:57 AM
I'm also desperately awaiting a solution to this problem which is the key limitation preventing SSAS MD cubes from scaling out in my environment. Our continued use of SSAS MD is at jeopardy without this being address and SSAS BISM is not a solution as our cubes are just far too large to be contained in RAM.
Posted by Simon12345 on 11/14/2014 at 1:43 AM
Any update on this? I know I'm cluchting at straws that this maybe addressed - but I would really really like to see it changed.
Posted by Microsoft on 1/20/2011 at 4:31 PM
Thanks a lot Greg for filing this suggestion

We will take a look.
Edward Melomed