I've implemented dimensional security through a UDF DLL and it works
perfectly unitl I process my cubes.

(Prior to implementation I applied the appropriate SPs and installed
the hotfix I got from Microsoft PSS as described here:
http://support.microsoft.com/?id=816480).

After I process a cube that uses my UDF for security, the reference to
the library that contains the UDF becomes invalid and the role doesn't
work.

To fix it I have to:
open the Cube Role, unregister the DLL in the "Allowed Members" MDX
Builder in the "Custom Settings" for the dimension, PROCESS THE CUBE,
register the DLL in the "Allowed Members" MDX Builder for the
dimension, PROCESS THE CUBE AGAIN, THEN enter the MDX that calls the
UDF in the "Allowed Members" box.

Any deviation from this algorithm generates one of several error
messages pertaining to COM or the MDX not parsing.

After I complete the above steps (exactly as described) everything
works perfectly UNTIL I PROCESS (nightly) and I have to
unregister/register the library in the cube role for each cube all
over again.

Any help is greatly appreciated.

Thanks,
Stewart

Stewart, can you try and register the library in the calculation editor of
the cube editor as opposed to in the calculation editor of the role manager.
Once you do that - I beleive all your problems will go away.

--
==================================================
Mosha Pasumansky - www.mosha.com/msolap
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================
"stewart whaley" <whaleysa (AT) archildrens (DOT) org> wrote

The way I do it is to bring up the cube editor, go to create a new
calculated member. Register the dll. Cancel out of the calculated member --
AND SAVE THE CUBE. What is happening under the covers is that when you
register the dll, a new COMMAND object is being added to the cube that
contains a "USE LIBRARY" MDX statement. You must *save* the cube, even
though it doesn't look like you've changed anything. If you don't save the
cube, then the dll registration is not saved.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Practices Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Mosha Pasumansky [MS]" <moshap (AT) microsoft (DOT) com> wrote

Thanks, Mosha, registering in the cube editor solves the problem.

I forgot to mention, as long as I process the cube via AS on the same
box everything works with the library only registered in the cube role.

My problems came up when my DTS jobs (running on another server)
processed the cubes.

Assuming no other issues arise from the UDF solution this method finally
allows us to address our stringent
security requirements.


*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Thanks, Dave, that explains everything.

I kept looking at the cube scripts I generate with "MetaDataScripter"
from the SQL Res Kit and didn't understand why there wasn't anything
that referenced the UDF library...I finally decided it must be something
internal that wasn't exposed!

This should solve a major need for extremely granular security solution
at my site. Prior to my arrival they were using nearly 700 Cube Roles
to administer security (everyone I've spoken to thinks we have the
record for number of cube roles on a single AS box).

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!