Modeling patterns for dynamic security

To create a model for dynamic security:
1. Create a two-column security table in the relational data source. In the first column, specify the list of Windows user names or custom data values. In the second column, specify the data values that you want to allow users to access for a column in a given table.
2. Import the security table into the tabular model using the Import Wizard.
3. Using the Import Wizard, create a one column table that contains the user names or custom data values for the model. The values in this table must be unique. This table does not need to be materialized in the relational data source; instead, it can be constructed in the Import Wizard by querying the security table for the unique user names or custom data values.
4. Create a relationship between the security table and the column that is being secured.
5. Create a relationship between the bridge table created in step 3 and the security table created in step 2.
6. [optional] Add supporting calculated columns or measures for computing the row filter on the table that contains the column that you want to secure.
7. Create a role in the Role Manager with Read permission.
8. Set the row filter for the security table to =FALSE().
9. Set the row filter for the bridge table to restrict the allowed row set to the currently logged on Windows user or to the custom data value using a row filter like =[Column Name]=USERNAME() or =[Column Name]=CUSTOMDATA().
10. Set the row filter on the table that you want to secure using one of the methods described in the examples that follow.

Comments

Post a Comment

Popular posts from this blog

SSRS Report Design: Best Practices

Introduction Microsoft® SQL Server™ Reporting Services is a comprehensive reporting tool. In using Reporting Services, you can design and deliver a wide range of reports, from simple tables to online free-form reports with graphical items and interactive links. Reporting Services can render reports for a variety of client-viewing formats, including HTML, PDF, Excel, and image formats. The wide variety of options and choices can be problematic for report authors who must make numerous decisions when choosing how to lay out a report. This paper provides a few guidelines to make these decisions easier and answers common questions.
Read more

SSAS OLAP Design - Best Practices

Introduction This paper outlines the recommended best practices for designing OLAP databases in Microsoft SQL Server 2005 Analysis Services to better meet the functional and performance needs of users. Designing a database for Online Analytical Processing (OLAP) databases is very different from designing a database for Online Transaction Processing (OLTP) and requires a different approach for achieving optimal results. The best practices recommendations are grouped into the following sections: Data Source Design Best Practices Dimension Design Best Practices Cube Design Best Practices Partition Design Best Practices Aggregation Design Best Practices Within each section, these best practices are ordered roughly by priority, where priority is a combination of how important the best practice is and how often you must worry about it. Major topics not covered include best practices for the design of calculations and for server management and operations.  These two topics are s...
Read more

Enable Usage-Based Optimization in SSAS

Usage-Based Optimization is a fantastic feature in SSAS to improve the most frequently used MDX queries of any cube database. This feature is used to design aggregations based on actual user queries using Business Intelligence Development Studio. But when ever you try to design  Usage-Based Optimization  you might have seen all the options  disabled.  This uses the technique of creating aggregations on FREQUENTLY USED queries in the given time interval.  We can enable the options in Usage-Based Optimization wizard. Connect to SSAS using SSMS (Sql Server Management Studio). Right click on the server and select properties as shown below. set CreateQueryLogTable to  true. Set the value of  QueryLogConnectionString  to any database where you wish to store your queries. Set the value of  QueryLogSampling  to the appropriate value for your environment (the default value of 10 means every 10th query will be logged). The lowe...
Read more