Security Cell Security: when Read permissions are actually Read Contingent
| Cell Security: when Read permissions are actually Read Contingent |
| Written by Chris Webb |
| Tuesday, 20 May 2008 21:20 |
|
I usually avoid using cell security like the plague for the good reason that it absolutely kills query performance. But sometimes there's no alternative but to use it and I'm working on one such project right now. However I've found a new gotcha: the behaviour of cell security changed between AS2005 SP1 and SP2 and in my opinion it didn't change for the better. The short explanation is that when you are using just Read permissions in cell security, if you have MDX Script assignments at a lower level of granularity you'll find that the higher level members whose values are affected by the assignments have Read Contingent permissions applied to them, even though according to the MDX expression I used in for the Read permissions these values should not be secured. Read more... |
Latest Author Articles
- Reporting Services-generate MDX, Subselects and Formula Caching
- Calculated members are better than assignments to real members (at least sometimes)
- Using AS Data Mining to Add Forecast Values to a Cube
- Displaying totals at the bottom
- Generating large numbers of partitions using Excel
Top Rated
- SSAS Implementation Best Practices slides in PDF format
- SSRS Report Against a SSAS Parent Hierarchy
- Handling inter-dimensional members dependency and reducing cube sparsity using reference dimensions in Analysis Services 2005
- Cube structure optimization for MDX query performance in Analysis Services 2005 SP2: Tips for Parent Child Hierarchies usage
- Handling Multiple Calendars with a M2M Scenario
- Passing MDX parameters in Reporting Services reports
- Using UserName to Control Data Access and Default Member in SSAS 2K5 (Carrie Williams)
- SSAS Tutorial: SQL Server 2005 Analysis Services Tutorial by Accelebrate
