![]() ![]() Especially in combination with ASSP this can be quite powerful as you can use any datasource that you can query using. Basically, when a user connects it queries internal data (within the cube using MDX) or external data (using Analysis Services Stored Procedure (ASSP)/Assemblies) to get the security settings for the current user. So for our example from above instead of having 100 different roles we would end up having one dynamic role serving all 100 users. Dynamic Security is evaluated at runtime for each user and allows you to consolidate your roles. To address this issue Analysis Services offers the concept of Dynamic Security. ![]() In terms of maintenance this can get quite complex and in the long run unmanageable. Each of this KeyAccounts is managed by one user, so we would end up creating 100 roles – one for each KeyAccount and its manager. Just think of an Analysis Services that holds sales data associated to KeyAccounts – further assume that we have 100 KeyAccounts. Though, also Dimension Data Permissions can get quite complex, especially for large-scale cubes with 100+ or even 1000+ users. Dimension Data Permissions are usually the way to go and can cover probably 98% of the security requirements. Because of the huge impact on performance Cell Data Permissions are barely used. Analysis Services Multidimensional in general offers two option on how to define security: Cell Data Permissions and Dimension Data Permissions. ![]() Especially for big enterprise solutions the security-concept can become very complex. Security is always an important aspect of any BI solution. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |