Article ID: 275919 - View products that this article applies to.
This article was previously published under Q275919
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 11214 (PLATO7x)
When you edit a partition or attempt to perform any action on a partition through the OLAP Manager such as the Usage-Based Optimization Wizard, the OLAP Manager may run out of stack space and stop responding (hang).
When there are a large number of partitions with a blank aggregation prefix, the OLAP Manager must make calls to create a default prefix. To do this, the OLAP Manager goes through all of the partitions in all of the cubes, and if there are too many partitions, the OLAP Manager runs out of stack space.
To work around this problem, make sure that all partitions have an aggregation prefix, which is a name to uniquely identify the partition for the cube. To assign an aggregation prefix to a partition, perform the following steps:
To preserve backward compatibility, this limitation still appears for cubes with the relational OLAP (ROLAP) storage type. To avoid this problem for ROLAP, see the "Workaround" section.
For more information on the aggregation prefix, see the "AggregationPrefix Property" topic in the product documentation.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in SQL Server OLAP Services 7.0 Service Pack 3. For more information, contact your primary support provider.
To resolve this problem, obtain the latest service pack for SQL Server OLAP Services 7.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301511This problem does not occur in Analysis Services 8.0.
(http://support.microsoft.com/kb/301511/EN-US/ )INF: How to Obtain the Latest SQL Server 7.0 Service Pack