We were creating local cubes in AS 2000 using the connection string method.
As this is no longer supported for AS 2005, we have changed to using the
CREATE GLOBAL CUBE MDX statement. Everything is working, but the local cube
files that are generated are 10 to 20 times the size that were generated
against AS 2000.

I have isolated this problem to one very large dimension. Because the
CREATE GLOBAL CUBE populates the cube with data in addition to creating it,
the entire dimension is copied into the local cube file. However, due to
correlations with another dimension (which is being filtered), only a small
subset of the dimension is required.

Any advice on how to accomplish this with AS 2005?

In AS2000 all dimensions in local cube were private dimensions which were
built from fact table - but private dimensions are not supported by AS2005,
therefore you are getting the full dimension.which

--
==============================*=================== =
Mosha Pasumansky - http://www.mosha.com/msolap
Analysis Services blog at http://www.sqljunkies.com/WebL*og/mosha
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==============================*=================== =
"Richard Cote" <RichardCote (AT) discussions (DOT) microsoft.com> wrote

Thanks for the explanation, but I still need a resolution to the problem.
Sending larger local cube files is not an acceptable solution.

"Mosha Pasumansky [MS]" wrote:

Does anyone have any suggestions on how to work around this issue in AS 2005?
Or do I need to roll back to AS 2000?

"Mosha Pasumansky [MS]" wrote: