SSAS\MOLAP Does not allow change in AttributeHierarchyOptmizedState - by Bob Duffy

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


3
0
Sign in
to vote
ID 872497 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 5/13/2014 3:24:19 AM
Access Restriction Public

Description

If turn off bitmap indexes on a shared dimension in SSAS/MOLAP by setting the AttributeHierarchyOptmizedState to false it will also update within the copy of the dimension within the cube. However if we then set the AttributeHierarchyOptmizedState back to true in the shared dimension it does NOT update in the cube, resulting in an inability to turn bitmap indexes back on for a customer.

Sign in to post a comment.
Posted by Microsoft on 5/15/2014 at 11:31 AM
Hi Bob,

Thanks for reporting this issue. It is intentional that disabling indexes on the dimension will disable it in all cubes. The behavior should be as follows:
- If dimension has AHOS=Disabled, all cubes must have it disabled
- If dimension has AHOS=Enabled, each cube can customize the state for the attribute and choose whether to enable or disable the indexes by setting it on the CubeAttribute object

This behavior allows an administrator to globally disable indexes for an attribute across all cubes. But it also allows each cube extra control so that individual choices can be made on a per-cube basis.

Thanks,
The Analysis Services Team