I have a relatively large cube that when I try to open it up via the cube browser utility in SQL Server Management Studio, it takes approximately 25 minutes for the cube browser utility to open up. If I want to query the database via MDX, the MDX writing utility (right-click on the database->New Query->MDX) comes back really fast (within a second).
What does the browser utility do differently that requires it to take so long versus the query utility?
Is there a way to speed it up?
Thanks
Hi there:
This is happening because the default query bein generated by the browser is taking a huge time to execute. Try using a simpler (read:less calculation intensive) measure as your cube default and watch the browser fly.
Hope that helps.
Cheers.
Suranjan Som
Senior BI Architect
Information Managment Group
|||
Unfortunately, this does not solve the problem. I turned on SQL Server Profiler and noticed that for each measure group in the cube (this particular cube has 12) it has to read in each partition. 6 of these measure groups have 48 combined partitions. Why does it need to read in each measure group? Unless there is a setting that I am missing, this is going to be an issue for anybody that has a large cube (billion plus rows) with multiple partitions.
No comments:
Post a Comment