FIX: Copied Cubes with Private Dimensions May Fail to Paste into New Databases (239441)


The information in this article applies to:

  • Microsoft SQL Server OLAP Services 7.0
This article was previously published under Q239441

SYMPTOMS

When attempting to copy a cube from one database to another using the OLAP copy/paste add-in, where that cube contains one or more private dimensions, the cube will be created on the destination database without any dimensions either public or private.

STATUS

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 1. For more information, contact your primary support provider.

RESOLUTION

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:

301511 INF: How to Obtain the Latest SQL Server 7.0 Service Pack

MORE INFORMATION

The user might encounter the same problem while using the clone method of clsCube from DSO.

This behavior is not seen when the cube is cut and paste within the same database. That is, the cube is created with both public and private dimensions.
Modification Type:MajorLast Reviewed:10/16/2003
Keywords:kbBug kbfix KB239441
©2003 Microsoft Corporation. All rights reserved.