Quote:> Rather than giving employee's a role/privilege is it viable to just give
> them access to a view that allows them to SELECT, UPDATE, DELETE, INSERT
> 2 tables?
We are using DSO to find the roles that are included in a cube. We have
discovered the following behavior:
1. If a new database role is added using the Analysis Manager, but that new
role is not added to the cube, that role does not show up in the collection
of roles for the cube. Very good.
2. If that database role is added to the cube using the Analysis Manager,
that role appears in the collection of roles for the cube. Also very good.
3. But if that role is removed from the cube (by unselecting the role in the
Manage Roles dialog for that particular cube), the role still appears in the
collection of roles for that cube.
Using DSO (or ADOMD), is there any way to tell that a particular role is no
longer valid for that cube? Is there any way we can query the collection of
cube roles so that these removed roles will not be included?
We are now doing this by opening an ADOMD connection to the cube, using each
role, and checking to see if that role is still valid. If it has been
removed, any MDX statement issued on the connection will fail. This solution
is too time-consuming and takes too much memory, so we're looking for a
6. SQL speed