Is there a way to implement security that has been designed at the database level for the DC? I know that the obstacle is that the cube, due to caching, will not always make a connection back to the database so as to make use of the security...but I am hoping that I can get some other ideas of how to best utilize the security model ???
The common approach is to create Security Views within the Cube Designer, or importing the database model into Cube Designer as a siloed Query Subject to apply security...but I am not sure how we could create a hybrid of these to work similar to how the database security works with FM on a relational side???
I hope this question is clear...please advise if it does not.
Thanks
QuoteI hope this question is clear..
Not really actually; not sure what you are seeking.
The only way to do security is via security views.
10.2.2 has lookup table- based security. The administration of which is a bit easier than role-based security. Presumably lookup table security's what you're getting at when you talk about 'a siloed Query Subject', and you don't think it suitable for your purposes. Could you be kind enough to define the problem that you are encountering in more detail please. In your answer could you explain how lookup table security isn't the bee's knees. I think you can think of them in terms of being roughly analogue to FM data security filters.
https://www.youtube.com/watch?v=Fxb27_e6IH0
http://www.redbooks.ibm.com/abstracts/sg248064.html?Open