Technical: Microsoft – SQL Server – Analysis Services – Deployment – Error – The full error message is “SSAS Error: Errors in the OLAP storage engine: A duplicate attribute key has been found when processing: Table: , Column: . Value: . The attribute is .”

Technical: Microsoft – SQL Server – Analysis Services – Deployment – Error – The full error message is “SSAS Error: Errors in the OLAP storage engine: A duplicate attribute key has been found when processing: Table: , Column: . Value: . The attribute is .”

Background

When trying to deploy a Microsoft SQL Server Project ran into this error message “Technical: Microsoft – SQL Server – Analysis Services – Deployment – Error – The full error message is “Errors in the OLAP storage engine: A duplicate attribute key has been found when processing: Table: , Column: . Value: . The attribute is .” ”

Error

Here is the actual error image:

ADuplicateAttributeKeyHasBeenFoundWhenProcessing

Solution Options

Looked at the problem a few times and tried a couple of pathways.

Key Columns

The most common cause is not properly identifying key columns for each attribute.  And, so please select the Dimension.  And, on each Dimension Attribute, ensure that you have fully stated the Key Columns.

This is especially important for composite keys or Hierarchic data.  i.e.

  • School Name
  • City
  • County
  • State
  • Country

In the example above, there are certain popular school names such as Kennedy High School that can be repeated across  Cities, Counties, States, and Countries.

So you might want to access the key columns and help the engine by listing all the columns that makes it unique; usually you start off with the key column – a numeric ID, and then stating the widest area and narrowing it as you come down.

So we might end up with:

  • StateID
  • SchoolName
  • City
  • County
  • State
  • Country

Our Solution

In our case, the problem was that when we added a new dimension and defined its relationship with the Fact table, the system somehow added an attribute from the Fact table.

We removed it, fully rebuilt the project, and re-deployed the project.

Also, under “Process Options” you might want to choose “Process Full” to ensure that a full rebuilt is occurring.

ProcessDimension - [Dimension]

References

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s