Microsoft KB Archive/231357

= BUG: Structural Changes to a Shared Dimension Fail to Write-Disable Cubes =

Article ID: 231357

Article Last Modified on 10/16/2003

-

APPLIES TO


 * Microsoft SQL Server OLAP Services

-



This article was previously published under Q231357



BUG #: 380 (plato7x)



SYMPTOMS
When you change the structure of a shared dimension (in the Library folder) used in a write-enabled cube (for example, you add or delete a level), the cube stays write-enabled and you do not get any warning. If you process this cube, it remains write-enabled. This situation is problematic because:
 * After processing the cube's data does not reflect the write-back data.
 * The cube's write-back table is inconsistent with the revised shared dimension.



WORKAROUND
To prevent this problem, before making structural changes to a shared dimension, write disable the write-enabled cubes that include the dimension. Use one of the following procedures to do that:
 * If you are using OLAP Service Enterprise Edition, you can convert the write back data to a partition that will incorporate the write-back data into the cube and make the cube write disabled. To do that right-click the cube, point to Write-Back Options, and click Convert to Partition. Next, use the Convert to Partition dialog box to convert the write-back data to a partition. NOTE: This option is not available with the Standard Edition.
 * If you are using the Standard Edition, you will have to delete the write back data before write disabling the cube. To delete the write-back data, right-click the cube, point to Write-Back Options, and click Delete Data. This will write disable the cube.

NOTE: The following procedure will delete the cube's write-back table.

If you have already made structural changes to a shared dimension, right-click the write-enabled cube that includes it, point to Write-Back Options, and click Delete Data. This action write-disables the cube.

Repeat the preceding procedure for each write-enabled cube that includes the shared dimension.



STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0.



MORE INFORMATION
Also note that whenever a structural change is to be made to a write-enabled cube, it must be write-disabled first because its structure is no longer consistent with its write-back table. If you make any structural change within a write enabled cube, for example add a dimension, a dialog box opens in OLAP Manager that contains a warning message with the caption 'Delete Write-Back Data':

This will delete the data in the write-back table and convert your cube to a read-only structure.

Caution: All write-back data will be deleted.

Are you sure you want to proceed?

If you click Yes, the cube is write disabled and all read/write permissions for the cube are disabled.

If the user makes a nonstructural change, such as changing a measure's Data Type property in the cube, the cube remains write-enabled. This situation is normal.

Keywords: kbbug kbpending KB231357

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.