Hi,

We have a cube with 70 Dimensions and 8 Measures. The total size is around
175 MB. We are displaying this in front end using Office Web Components.

After the cube name has been clicked, it takes 2-3 minutes to load the cube
details.

Can anyone please let us know how we can improve on the performance and
reduce the time to load the cube details.

--
Thanks!
--SHC

Hell....... any user who can successfully manage a cube with 70 dims must
have the brains the size of a planet.

Joking aside, try reducing the the number of dimensions and increase the
number of cubes to suit the different user base. If your clients won't accept
that because one day next year thet may want to use a dim they diddn't even
know was there then I suggest a good partition strategy.

"OLAP_SHC" wrote:

OLAP Gurus,

Partitioning the cube is not affecting the time to load the cube. Any other
tips?

Thanks in advance!
--SHC

"HWUK" wrote:

really you should reduce the dim count but....

one thing you could look at is the connectionstring properties, in particular the client cache size and large level threshold. The first will let you limit the amount of memory that PTS uses on the client, the second will let you specify what is a large dimension and therefore what dimensions get fully loaded to the client.

The latter will probably help you out, but, I have seen people who then have problems becuase if all the dim members haven't been loaded to the client, then some dimension members will appear to 'not exist' to the client.

HTH,

Steve

*****************************************
* A copy of the whole thread can be found at:
* http://www.sqlmonster.com/Uwe/Forum....rver-olap/4504
*
* Report spam or abuse by clicking the following URL:
* http://www.sqlmonster.com/Uwe/Abuse....b07a3d8e160d6a
*****************************************