Microsoft KB Archive/317258

= PRB: Member Key Column for Parent-Child Dimensions Must Be Unique =

Article ID: 317258

Article Last Modified on 2/20/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Analysis Services

-



This article was previously published under Q317258



SYMPTOMS
If you create a parent-child dimension that contains non-unique member keys or parent and child columns with different data types, an error message similar to the following occurs:

Processing Error [The dimension member key is not unique] 51100



MORE INFORMATION
A parent-child dimension is based on two dimension table columns that together define the lineage relationships among the members of the dimension. The member key column identifies each member, while the parent key column identifies the parent of each member. Analysis Services uses this information to create parent-child links, which it combines into a single member hierarchy that represents a single meta data level. If you create a parent-child dimension, the values contained in the member key column for each member of the dimension must be unique and the data type for the member key column must be the same as the data type for the parent key column.

If the member key column contains non-unique members, an error message similar to the following occurs:

Processing Error [The dimension member key is not unique] 51100

If the data type for the member key column does not match the data type for the parent key column, the following error message occurs when Analysis Services processes the dimension:

Processing Error [The dimension member key is not unique] 31100

The following error message occurs if you try to browse the dimension data:

Invalid parent-child in level level_name

Parent Key Column must be of the same data type as Member Key Column

Steps to Reproduce Behavior
To reproduce the dimension member key with the non-unique error message, follow these steps:

 Open the FoodMart 2000.mdb database. Create a new table named uniqu_data with the following structure:

 Populate the uniqu_data table with the following values:

  Create a new parent-child dimension and use the uniqu_data table as the data source, with the following properties: Member Key = Member_Key Parent Key = Parent_Key Member Name = Member_Key  Save, and then browse the dimension.

To reproduce the invalid parent-child error message, follow these steps:  Open the FoodMart 2000.mdb database.</li> Create a new table named mixed_data, with the following structure:

</li> Populate the mixed_data table with the following values:

</li>  Create a new parent-child dimension and use the mixed_data table as the data source, with the following properties: <pre class="fixed_text">Member Key = Member_Key Parent Key = Parent_Key Member Name = Member_Name </li> Save, and then browse the dimension.</li></ol>

To avoid these issues when you create a parent-child dimension, make sure that the member key column for each member of the dimension is unique and that the data types for the member key and parent key columns are the same.

Additional query words: Parent Child DataType OLAP

Keywords: kbprb KB317258

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.