dbTalk Databases Forums  

The dimension member key is not unique

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap


Discuss The dimension member key is not unique in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Mike A.
 
Posts: n/a

Default The dimension member key is not unique - 12-22-2003 , 05:31 PM






I want to use a view as a dimension that has the following
structure:

AccountKey
AccountNumber
LineOfBusinessLevel1
....
LineOfBusinessLevel4

Hierarchically, the dimension looks like this (from top to
bottom)

LineOfBusinessLevel1
....
LineOfBusinessLevel4
AccountNumber

The Line of business hierarchy changes over time and the
underlying dimension table reflects the profile of the
account at the time of the fact's occurrence. AccountKey
will be different for each profile of the account, but the
AccountNumber will not change.

When processing the cube, the above-referenced error is
returned for the AccountNumber column. What can I do to
fix this problem? My users need to drill up and down the
hierarchy...

TIA,

Mike

Reply With Quote
  #2  
Old   
Jeremy Highsmith
 
Posts: n/a

Default Re: The dimension member key is not unique - 12-22-2003 , 09:03 PM






Hi Mike - Try changing the member keys unique property to false at the
dimension and account level. If your member key = member name, then
also set the member name property to false and set "allow duplicate
member names" = True at the dimension level. Hope that helps.


"Mike A." <anonymous (AT) discussions (DOT) microsoft.com> wrote

Quote:
I want to use a view as a dimension that has the following
structure:

AccountKey
AccountNumber
LineOfBusinessLevel1
...
LineOfBusinessLevel4

Hierarchically, the dimension looks like this (from top to
bottom)

LineOfBusinessLevel1
...
LineOfBusinessLevel4
AccountNumber

The Line of business hierarchy changes over time and the
underlying dimension table reflects the profile of the
account at the time of the fact's occurrence. AccountKey
will be different for each profile of the account, but the
AccountNumber will not change.

When processing the cube, the above-referenced error is
returned for the AccountNumber column. What can I do to
fix this problem? My users need to drill up and down the
hierarchy...

TIA,

Mike

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.