Database Reference
In-Depth Information
As you can see from the results, you get data for both
Europe
and
North America
.
This happens even though the
North America Reader
role explicitly denies reading
data for Europe.
Implementing dynamic data security
Using a security model built using conventional roles can be troublesome to main-
tain, if you are working with a large Analysis Services implementation. The solution
tothisistousedynamicsecurity.
Dynamic security
givesyoutheability touseMDX
functions to check the users that connect to the cube and apply the user rights based
on the user that connects.
To implement dynamic security, you need to add information to your cube containing
the Windows username. In the database that is used in this topic, you have a table
called
DimEmployee
that contains a row for each employee in the company. One
of the columns contains the Windows NT username. This column can be used in an
MDX function that will filter the data so that a user only can see their information and
the users appearing below him or her in the hierarchy:
In order to test dynamic security, you need to change the value in the
LoginID
column to contain information that is relevant to your environment. Now, the
Lo-
ginID
column contains the Windows username that is valid for the
Adven-
Search WWH ::
Custom Search