Technical Training
Analysis Services TrainingTable of Contents
MSAS - Applying security to a Dimension
MSAS - Applying security to a Dimension - Page 2
MSAS - Applying security to a Dimension - Page 3MSAS - Applying security to a Dimension Page - 3
MSAS - Applying security to a Dimension
In the Cube Role manager for the sales cube select the All users role and click the ellipsis button in the Restricted dimensions column.
Select the time dimension and then select custom from the Rule drop down list. Then click the ellipsis button to open the Custom Dimension security dialog box. In the common tab select the check box for defining a default member. Note that an MDX expression has to be specified.
|
|
Click Ok three times in the screens that follow. The members function retrieves a set of all the members of the Calendar year level, while the Tail function forms a set that consists of only the last member from the level. The Item function extracts the first and the last member of that set. The resultant values are the last member of the Calendar Year level. Click the test role button to test the role.
Cell level security further restricts users from viewing certain cell values. Most often dimension level security is sufficient to ensure that the values of the cells in the restricted dimension are not visible. Yet when the cells need to be secured without removing members in a dimension then, cell level security is useful.
Right click the cube for which you want to apply cell level security and click manage roles. Expand all the levels and click Test role. Browse the data. Note that all the cells contain values. Close the Browser window and Click on the Cells column ellipsis button. The default Cell security policy value is unrestricted read. Select Advanced from the drop down list.
|
|
Select custom in the rule column and click on the ellipsis button in the custom settings column. Type a description in the description box. The cell security needs an MDX expression that can be calculated for each cell of a grid so that the value evaluated returns a false and nothing will be displayed to the end user.
|
|
Check the syntax by clicking the Check button if required. If the syntax is valid Analysis services says so. Close the message box and proceed.
The Read Contingent and Read/write permission for the role are automatically set to Fully restricted. Close the Edit cube dialog box and browse the data. The restricted cells will have #N/A against their value.
Cell level security is extremely important in write enabled cubes. Different groups of people may modify different cell values causing loss of integrity of data. To enable members to write to a cube the cube must be write enabled.
Analysis services gives a lot of importance to security. The cube role manager provides the administrator with flexibility for applying security. He can set permission at various levels beginning with the server itself and going down to the cell in a cube. Fine tuning of security can be done using MDX expressions.
In the next lesson we shall learn how to create and implement data mining models
Analysis Services Training
- MSAS - Browsing the Dependency Network
- MSAS - Building a Relational Decision Tree Model
- MSAS - Introduction to Data Mining
- MSAS - Applying security to a Dimension
- Tutorial 65: MSAS - Managing Cube Roles
- MSAS - Understanding Database Roles
- MSAS - Securing User Authentication
- MSAS - Introducing Analysis Services Security
- MSAS - Writebacks
- MSAS - Defining and Creating Drillthrough
- MSAS - Defining and Creating Auctions
- MSAS - Creating and Maintaining Calculated Members in Virtual Cubes
- MSAS - Building a Virtual Cube
- MSAS - Understanding Virtual Cubes
- MSAS - Introducing Solve Order
- MSAS - Implementing Calculations Using MDX Part 2
- MSAS - Implementing Calculations Using MDX Part 1
- MSAS - Merging Partitions
- MSAS - Introduction and Managing Partitions
- MSAS - Troubleshooting Cube Processing
- MSAS - Optimizing Cube Processing
- MSAS - Processing Dimensions and Cubes
- MSAS - Introducing Dimension and Cube Processing
- MSAS: Optimization Tuning Part 2
- MSAS: Optimization Tuning Part 1
- MSAS: Usage-Based Optimization
- MSAS: Analysis Services Aggregations
- MSAS: The Storage Design Wizard
- MSAS: Analysis Server Cube Storage
- MSAS: Defining Cube Properties
- MSAS: Introduction and Working with Measures
- MSAS: Introduction and Working with Cubes
- MSAS: Virtual Dimensions
- MSAS: Introducing Member Properties
- MSAS: Creating Custom Rollups
- MSAS: Creating a Time Dimension
- MSAS: Understanding Hierarchies
- MSAS: Dimension Storage Modes and Levels
- MSAS: Working with Levels and Hierarchies
- MSAS: Working with Parent-Child Dimensions
- MSAS : Basics of Levels
- MSAS : Working with Standard Dimensions
- MSAS : Shared vs Private Dimensions
- Understanding Dimension Basics
- MSAS : Office 2000 OLAP Components
- MSAS : Client Architecture
- MSAS : Cube Storage options
- MSAS : Meta data Repository
- MSAS : Analysis services Tools for Extended Functionality
- MSAS : The Wizards
- MSAS : The Analysis Manager and Analysis Server
- MSAS : The Data warehousing framework of SQL Server 2000 - Part 2
- MSAS : The Data warehousing framework of SQL Server 2000 - Part 1
- MSAS : Microsoft Data Warehousing Overview
- MSAS : Browsing the Cube
- MSAS : Designing Storage and Processing the Cube
- MSAS : Building the Cube Part #3
- MSAS : Building the Cube Part #2
- MSAS : Building the Cube Part #1
- MSAS : Setting up the Database in Analysis Server
- MSAS : Preparing to Create the Cube
- MSAS : Introducing Analysis Manager Wizards
- Microsoft Analysis Services Installation
- MSAS - Applying OLAP Cubes
- Understanding OLAP Models
- Designing the Dimensional Model and Preparing the data for OLAP
- Design of the data warehouse: Kimball Vs Inmon
- Defining OLAP Solutions and Data Warehouse design
- Microsoft Analysis Services Training
- Data Warehouse database and OLTP database
- Introduction to Data Warehousing










