dbTalk Databases Forums  

Error processing cube with disabled lowest level of shared dimension

comp.databases.ms-sqlserver comp.databases.ms-sqlserver


Discuss Error processing cube with disabled lowest level of shared dimension in the comp.databases.ms-sqlserver forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
SRL
 
Posts: n/a

Default Error processing cube with disabled lowest level of shared dimension - 04-05-2005 , 06:41 AM






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


Reply With Quote
  #2  
Old   
Simon Hayes
 
Posts: n/a

Default Re: Error processing cube with disabled lowest level of shared dimension - 04-06-2005 , 03:28 PM







"SRL" <srlanger (AT) gmail (DOT) com> wrote

Quote:
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




Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.