Hello All,

I read an article “Customizing Dimension Security” (InstantDoc #27305,
http://www.windowsitpro.com/SQLServe...05/pg/1/1.html)
of Russ Whitney and tried to reproduce it with FoodMart2000 database.
Unfortunately, it didn’t work for me

As described, I created a security fact table, which contains user ID,
customer ID and an access flag (1 access is allowed, 0 – not allowed). I also
created a new security cube that contains the new security fact table, user
and customer dimensions. After that I created a virtual cube that combined
new security and sales cubes, a new role for the virtual cube and added
FILTER MDX statement to the role as was described in the example.

When I then tested the role on the Cube Role window (the button Test Role),
the customers were filtered out, but if I try to view the cube in
Analysis-Manager they will not be filtered out - I can see all customers! Ok.
As I tested with the user, which is in the OLAP Administrators group, I can
understand, why I see even though all customers.
I created a local user (which is not in OLAP Administrators group) and tried
to access the cube with MDX Sample Application (or MS Excel), which I started
with theis user account, but I get an error “Unable to open connection”. But!
If I delete FILTER MDX statement from the cube role, I can connect to the
cube without any problem! Of course, I don’t have in this case the dimension
security that I would like to achieve with the FILTER MDX statement.

So I have two questions:
1. How I can test if the security work?
2. Why I can’t access the cube if I define the FILTER MDX statement for the
cube role and if I remove it from the role I can access it?

Some additional information:
I use MS Windows 2000, and Microsoft SQL Server 2000.

I've already checked following resources and didn't found a solution for my
issue.
http://support.microsoft.com/default...b;en-us;828343
http://www.mosha.com/msolap/samples/...20security.zip

All users are in the users table.

The cubes were processed without errors.

Thanks in advice,
Andrei Litovka

This is the error you get when you don't have access to the dimension at
all. If there was no allowed set members.

If you look in that zip file there is a text file which I show you
step-by-step instructions for setting them up.

--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Andrei Litovka" <Andrei Litovka (AT) discussions (DOT) microsoft.com> wrote