In AS 2005, drillthrough security conforms to dimension security, so do
you intend to restrict user access to the select few diagnosis codes in
general? If so, you could create a "Denied Set" with these codes:
http://msdn2.microsoft.com/en-us/library/ms175366.aspx
Quote:
|
SQL Server 2005 Books Online
|
Granting Custom Access to Dimension Data
...
Understanding the DeniedSet Property
The DeniedSet property uses an MDX expression to determine the attribute
members to which a database role is explicitly denied access (the denied
set). The denied set can include no, all (default), or some attribute
members. By default, no denied set is defined.
When the denied set contains only a specific set of attribute members,
the database role is denied access only to those specific members.
Specifically defining a denied set may affect the accessibility of
attribute members that are added after the denied set is defined.
When you define a specific set of attributes in the denied set, the
effect of this denied set on the accessibility of other attributes
depends on whether the ApplyDenied property is enabled. For example,
suppose there is a denied set on the State attribute and the ApplyDenied
property is enabled. In this case the database role will not be able to
access any of the Customer attributes for those states within the denied
set.
...
http://msdn2.microsoft.com/en-us/library/ms145964.aspx
Quote:
|
SQL Server 2005 Books Online
|
DRILLTHROUGH Statement (MDX)
...
Important:
Drillthrough security is based on the general security options defined
on the cube. If a user cannot get some data by using MDX, drillthrough
will also restrict the user in the exactly the same manner.
...
- Deepak
Deepak Puri
Microsoft MVP - SQL Server
*** Sent via Developersdex http://www.developersdex.com ***