Error processing cube with disabled lowest level of shared dimension

[SRL]

Hi,

This is probably a classic scenario with a shared dimension that we
need to use in different cubes, where all fact tables do not offer the
same level of detail. Dimension is snow-flaked.

The cube that's causing me troubles was designed by marking the lowest
dimension level Diabled and not Visible. This allows me to get rid of
one of the snow-flake tables (the one with the lowest level), thus
allowing an INNER JOIN with the remaining table which has a level of
detail corresponding to the fact table.

When processing the cube, I get a 'member with key '[blah]' was found
in the fact table but was not found in the level '[blah]' of the
dimension '[blah]'' that seems to indicate that none of my fact foreign
keys exist as primary keys in the dimension table. However if I then
attempt to query the cube, all data seems to be there.

Would anybody be in a position (and willing ;-)) to share his/her own
experience working around a similar issue?

Thanks,

SRL

[Simon Hayes]

"SRL" <sr******@gmail.com> wrote in message
news:11*********************@l41g2000cwc.googlegro ups.com...

Hi,

This is probably a classic scenario with a shared dimension that we
need to use in different cubes, where all fact tables do not offer the
same level of detail. Dimension is snow-flaked.

The cube that's causing me troubles was designed by marking the lowest
dimension level Diabled and not Visible. This allows me to get rid of
one of the snow-flake tables (the one with the lowest level), thus
allowing an INNER JOIN with the remaining table which has a level of
detail corresponding to the fact table.

When processing the cube, I get a 'member with key '[blah]' was found
in the fact table but was not found in the level '[blah]' of the
dimension '[blah]'' that seems to indicate that none of my fact foreign
keys exist as primary keys in the dimension table. However if I then
attempt to query the cube, all data seems to be there.

Would anybody be in a position (and willing ;-)) to share his/her own
experience working around a similar issue?

Thanks,

SRL

You might want to post in microsoft.public.sqlserver.olap, to see if you get
a better response.

Simon

[SRL]

Thanks, will do.