dbTalk Databases Forums  

Bigint failure in Parent-Child dimension

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


Discuss Bigint failure in Parent-Child dimension in the microsoft.public.sqlserver.olap forum.



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

Default Bigint failure in Parent-Child dimension - 02-09-2004 , 09:57 AM






Hi,

Does anybody know if there is a fix for the following problem:

- A parent-child dimension.
- Both "member key column" and "parent key column" are of type bigint.
- Values in columns are 10000000000000 or more.
- BTW There's no problem if the columns values or smaller numbers.
- When looking on the Data tab in the Dimension editor the first item is shown
- After that the following error message is shown:

(Unable to retrieve children: Member with the UniqueName [XXX].&[XXX] not found.)

Thanks,
Remco

Reply With Quote
  #2  
Old   
Bas Kersten [MSFT]
 
Posts: n/a

Default RE: Bigint failure in Parent-Child dimension - 02-10-2004 , 02:09 AM






Hi Remco,

We are working on an issue with these symptoms.

Could you go to this dimension in AS manager, select this p/c dimension,
select this level, go to advanced, change the "Key Data Type" for the level
to 'Varchar' and do a full process.

Please let me know if this work, if not let me know so that I will try to
reproduce your problem in house and take it from there.

Regards,
Bas

"This posting is provided "AS IS" with no warranties, and confers no
rights."


Reply With Quote
  #3  
Old   
Irina
 
Posts: n/a

Default Re: Bigint failure in Parent-Child dimension - 02-18-2004 , 02:25 AM



Have you tried to used Hotfix:
http://support.microsoft.com/default...;en-us;822838?

Hope this helps,
Irina

"This posting is provided "AS IS" with no warranties, and confers no
rights."


""Bas Kersten [MSFT]"" <bask (AT) online (DOT) microsoft.com> wrote

Quote:
Hi Remco,

We are working on an issue with these symptoms.

Could you go to this dimension in AS manager, select this p/c dimension,
select this level, go to advanced, change the "Key Data Type" for the
level
to 'Varchar' and do a full process.

Please let me know if this work, if not let me know so that I will try to
reproduce your problem in house and take it from there.

Regards,
Bas

"This posting is provided "AS IS" with no warranties, and confers no
rights."




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.