![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
So, I can limit the region dimension to only show their region, but this approach fails when I use unrelated dimensions |
#3
| |||
| |||
|
|
Hello, I need help with OLAP security roles in SSAS. I am using the June CTP of 2005. I have figured out dimension member security, but the requirements of my security model require me to limit analysis from a regional level. What I mean about regional is that each role can only view information for their assigned region. So, I can limit the region dimension to only show their region, but this approach fails when I use unrelated dimensions. Then the analysis is back to allowing all fact records. Is there another way to enforce this type of security model? Thanks for any help you can provide. -Scott |
#4
| |||
| |||
|
|
So, I can limit the region dimension to only show their region, but this approach fails when I use unrelated dimensions Can you explain what do you mean exactly by this ? -- ==============================Â*================== == Mosha Pasumansky - http://www.mosha.com/msolap Analysis Services blog at http://www.sqljunkies.com/WebLÂ*og/mosha 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. ==============================Â*================== == |
#5
| |||
| |||
|
|
So, I can limit the region dimension to only show their region, but this approach fails when I use unrelated dimensions Can you explain what do you mean exactly by this ? -- ==============================Â*================== == Mosha Pasumansky - http://www.mosha.com/msolap Analysis Services blog at http://www.sqljunkies.com/WebLÂ*og/mosha 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. ==============================Â*================== == |
#6
| |||
| |||
|
|
What I'm trying to do is limit everything in the fact table by that dimension member. If I choose another dimension that has no hierarchy involving the Virginia member, I now have access to all the fact records. Including the one outside of Virginia. I'm trying to create a view of the facts (subset) forcing all facts to be driven by the Virginia member. |
#7
| |||
| |||
|
|
What I'm trying to do is limit everything in the fact table by that dimension member. If I choose another dimension that has no hierarchy involving the Virginia member, I now have access to all the fact records. Including the one outside of Virginia. I'm trying to create a view of the facts (subset) forcing all facts to be driven by the Virginia member. Perhaps I don't fully understand your problem, but it sounds like you should simply enable Visual Totals in dimension security... -- ==============================Â*================== == Mosha Pasumansky - http://www.mosha.com/msolap Analysis Services blog at http://www.sqljunkies.com/WebLÂ*og/mosha 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. ==============================Â*================== == |
#8
| |||
| |||
|
|
What I'm trying to do is limit everything in the fact table by that dimension member. If I choose another dimension that has no hierarchy involving the Virginia member, I now have access to all the fact records. Including the one outside of Virginia. I'm trying to create a view of the facts (subset) forcing all facts to be driven by the Virginia member. Perhaps I don't fully understand your problem, but it sounds like you should simply enable Visual Totals in dimension security... -- ==============================Â*================== == Mosha Pasumansky - http://www.mosha.com/msolap Analysis Services blog at http://www.sqljunkies.com/WebLÂ*og/mosha 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. ==============================Â*================== == |
#9
| |||
| |||
|
|
What I'm trying to do is limit everything in the fact table by that dimension member. If I choose another dimension that has no hierarchy involving the Virginia member, I now have access to all the fact records. Including the one outside of Virginia. I'm trying to create a view of the facts (subset) forcing all facts to be driven by the Virginia member. Perhaps I don't fully understand your problem, but it sounds like you should simply enable Visual Totals in dimension security... -- ==============================Â*================== == Mosha Pasumansky - http://www.mosha.com/msolap Analysis Services blog at http://www.sqljunkies.com/WebLÂ*og/mosha 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. ==============================Â*================== == |
![]() |
| Thread Tools | |
| Display Modes | |
| |