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

• Microsoft SQL Server OLAP Services version 7.0

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 this to be a problem in SQL Server OLAP Services version 7.0. This problem has been corrected in U.S. Service Pack 1 for Microsoft SQL Server OLAP Services version 7.0. For information about downloading and installing the latest SQL Server OLAP Services Service Pack, see http://support.microsoft.com/support/sql/.

For more information, contact your primary support provider.

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.

Additional query words:

Keywords : SSOSdso SSOSmgr kbbug7.00
Version : winnt:7.0
Platform : winnt
Issue type : kbbug