Note The space is not the number of rows in the fact table. The space is the full cross join space of all dimension granularity attributes. It takes a long time to enumerate those cells one-by-one in order to check the cell security.
Put the measures that should be secured into a separate cube, and implement the cube level write security under your role.
Note The performance when you use this method is as fast as when the query runs under an admin role. However, your cube design becomes complex, and you have to create virtual cubes to use linked measure groups in order to return the different measures in a single MDX query. Additionally, when you perform the writeback operation, you have to create an MDX query that uses the correct cube name based on the writeback measure.
Perform the writeback operation at the lowest granularity level of a certain member. You cannot allocate for many detailed granularity members.
Note You may have to create dummy members in dimension tables that are marked as adjustment members in each dimension, to support the writeback operation.
문서 ID: 2747616 - 마지막 검토: 2013. 2. 19. - 수정: 1