Hi,

I am trying to join two cubes together into a virtual cube, to implement
dynamic security. I have my main report cube which works and have created a
security cube which also works.

I've created the virtual cube to join the two cubes together and it
processes OK and I can browse the data.

However, I can only see the Fact data when all the dimensions are set to the
All Member. If I select a different member from a dimension for one cube, the
fact data from the other cube disappears, i.e. if I select a User from the
Security dimension in the Security cube, all the Facts disappear from the
reporting cube but the SecurityAccess measure from the security cube is
displayed correctly. If I select a member from any of the dimensions in the
reporting cube all the SecurityAccess values disappear. What's gone wrong...?

Thanks...

Hi,

As a starting point, this is basically how a virtual cube works!

As it states in the BOL: "When computing values in a virtual cube,
measure cells only contain values at the (All) level for dimensions that
are not common between the underlying cubes"

However, there is a workaround for this, namely the ValidMeasure
function (where the quote above is taken from actually!). This function
"returns the measure value from the cell at the (All) level coordinates
for the dimensions that are not common".

So, what you have to do is to make a calculated member, each using the
ValidMeasure([MyMeasure]), for each measure you have.

An entirely different matter is, that I don't quite understand, why you
make a cube to contain the security information - and how you aim to
make it work! - in stead of using the role based securitymodel, that is
contained is MSAS. But that's just me being a busybody... :-)

Best regards
Dan Reving

NeilBennettRBKC wrote:

Hi Dan,

Thanks for the info. I'll try that out.

The reason I am not using database roles is that I have approx. 500 Business
Units and approx. 100 Users, who each need to see a different range of Units.
According to what I have read, Analysis Services cannot scale to this number
of roles, so it needs to be done dynamically, using a security cube to
control who can see what and linking that to the data cube, through a virtual
cube. Only one database role is then required for all the Users.

Regards,
Neil

"Dan Reving" wrote: