Hi

I am using Microsoft Analysis Server SP3. On Browsing the dimension data in the Analysis manager tool manager I wrongly get below error
(Unable to retrieve children: Key is not unique in collection

The dimension is a simple parent-child dimension created using the Analysis Manager Dimension wizard

My dimension table structure is below in the SQL Server 2000 relational database

create table test_di

poolkey numeric (19)
poolname varchar(15)
parentkey numeric(19


Data which I insert is

insert into test_agencypool values (7070932889948389377, 'Enterprise', NULL
insert into test_agencypool values (7070932889948389378, 'Unassigned', 7070932889948389377

The OLAP dimension connects back to the above relational tables using OLAP Data Source
created in Analysis Manager and set to "Microsoft OLE DB Provider for SQL Server"

If I change the poolkey, and parentpoolkey of the test_dim relational table to VARCHAR(19), I don't get any error on browsing the data in OLAP dimension data browser

Any ideas as to how I can avoid the above error in the Analysis Manager when using NUMERIC keys

I am trying to avoid sending our product to production with VARCHAR data keys

Please hel

-Rajesh Digh
Primavera System

....One more thing.

When it works with VARCHAR(19) keys, I correctly see the below dimension hierarchy in Analysis Manager (Browse dimension data window)

All Test Dim
Enterprise
Unassigned.


During the problem symptom with NUMERIC keys, only below truncated dimension hierarchy is seen:

All Test Dim
Enterprise

As seen above, the "Unassigned" leaf level data is not shown by the Analysis Manager

-Rajesh

By some trial and error I came to this workaround.

In Analysis manager: Set the Member key column property of the test dimension to
convert(varchar(19),"dbo"."test_dim"."poolkey")

This avoids the problem.

As per may analysis this is a bug in the analysis manager wherein it cannot handle large keys values like:
7070932889948389377 in the dimension metadata.

It would be nice if a fix for this problem is available from the Microsoft Analysis Server support team.

Appreciate a comment from the Microsoft folks regarding the same.

Thanks
-Rajesh

This bug was reported earlier on this newsgroup (for SP2 in Nov. 2002).
Your example works with smaller key values:

http://groups.google.com/groups?hl=e...8&th=32a7021c1
4728848&rnum=3
I have narrowed it down:
members of my "big int" dimension can be referenced as long as their key
values are in the INT area,
i.e. key value is less than 2,147,483,647.
In other word BIG INT works only for INT?
I've set:
Key Data Size = 8
Key Data Type = Big Integer
in the dimension editor!
Is there anything more to set? Or is this a bug?
...
Igor, Im having the exact same problem as you.

1) Bigint dimensions creating 'cannot find dimension member in a name
binding function' error

2) only happens when the number is actually in the BIGINT range, if it
is still in the INT range, drilling down on the dimensions work

Has anyone talked to Microsoft yet about this?

- Deepak

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!