Auerelio Vasquez
asked on
Dimension Duplicate Key Error
when i try to process the date dimension, i get these errors when processing.
Errors in the OLAP storage engine: A duplicate attribute key has been found when processing: Table: 'dbo_dim_Date', Column: 'YearName', Value: '2006'; Table: 'dbo_dim_Date', Column: 'QuarterName', Value: 'Q1 2006'. The attribute is 'Quarter Name'.
Almost every dimension that i have , is getting similar errors when processing. Any ideas ?
Errors in the OLAP storage engine: A duplicate attribute key has been found when processing: Table: 'dbo_dim_Date', Column: 'YearName', Value: '2006'; Table: 'dbo_dim_Date', Column: 'QuarterName', Value: 'Q1 2006'. The attribute is 'Quarter Name'.
Almost every dimension that i have , is getting similar errors when processing. Any ideas ?
What database are you using?
What indexes do you have on the table in question? You need to look at them closely to make sure that you have not defined a Unique Index that doesn't allow the particular insert if that insert is actually needed.
ASKER
I'm using SQL Server2008R2.
As far as indexes, one is a date dimension, so it's not indexed, and the others just uses a primary key, all of which are used soley for identity.
As far as indexes, one is a date dimension, so it's not indexed, and the others just uses a primary key, all of which are used soley for identity.
Hi,
I suspect you have multiple members in your date dimension that have the same quarter name (makes sense) but that you have also marked the quarter name atttribute as needing to be unique.
Check the MemberNamesUnique property for the QuarterName atribute and try setting this to False.
Presumiably you could have problems with yearName, MonthName etc.
Depending on how you've structured your other dimensions / attribute hierarchies you may have problems elsewhere too.
Tim
I suspect you have multiple members in your date dimension that have the same quarter name (makes sense) but that you have also marked the quarter name atttribute as needing to be unique.
Check the MemberNamesUnique property for the QuarterName atribute and try setting this to False.
Presumiably you could have problems with yearName, MonthName etc.
Depending on how you've structured your other dimensions / attribute hierarchies you may have problems elsewhere too.
Tim
ASKER
I thought that may be the case as well, after diong further reading, but the hierarchy that i'm using, the columns are all MemberNamesUnique = False....
ASKER
let me see if i can explain his better:
so, for attributes of yearName, Quartername, MonthName i want to use as hiearchy. I set the visible property to false. Also i set up the keys like this:
YearName -
Properties - KeyColumns (collection) wk_Date, YearName: NameColumn = YearName
QuarterName-
Properties - KeyColumns(collection) yearname, quartherName NameColumn = QuarterName
MonthName
Properties - KeyColumns(collection) QuarterName, MonthName NameColumn = MonthName
I attached a screenshot of the attribute Relatinship:.... I still get a squiggly line in the hierarch saying no relationships have not been defined.... Also the reltinshiptypes are all flexible.
Thanks for your help.
dimTime.PNG
so, for attributes of yearName, Quartername, MonthName i want to use as hiearchy. I set the visible property to false. Also i set up the keys like this:
YearName -
Properties - KeyColumns (collection) wk_Date, YearName: NameColumn = YearName
QuarterName-
Properties - KeyColumns(collection) yearname, quartherName NameColumn = QuarterName
MonthName
Properties - KeyColumns(collection) QuarterName, MonthName NameColumn = MonthName
I attached a screenshot of the attribute Relatinship:.... I still get a squiggly line in the hierarch saying no relationships have not been defined.... Also the reltinshiptypes are all flexible.
Thanks for your help.
dimTime.PNG
In your image there is a golden key next to QuarterNumber. That induicates that it is a Primary Key . . . which means that it has to be unique. In other words, you can have only one entry with any given querter number.
Add an Identity column as your Primary Key and then make a Non-Unique Index on your QuarterNumber column. alternatively, you could make a Unique Index on YearNumber, QuarterNumber, MonthNumber, DayNumber.
Add an Identity column as your Primary Key and then make a Non-Unique Index on your QuarterNumber column. alternatively, you could make a Unique Index on YearNumber, QuarterNumber, MonthNumber, DayNumber.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
i thought the golden key is on wk_Date ? i don't see the key your are referring to in the image ??
ASKER
i got that to process by not having the key column collection in the relatinoship attributes. I'm confused by this, becuase it seems to be not using the best practices....
In the Attribute Relationships panel (centre bottom) the first relationship listed is Quarter Name -> Month Name. This is the wrong way around. You could try removing it and relying on relationships from your wk_Date attribute, but i think you may need to add Month Name -> Quarter Name to get it to process.
Tim
Tim
8080 Diver: the key is next to wk_date, I think (although it's not fully visible). This looks correct to me.
There's no need to add an identity column if the date is unique.
Tim
There's no need to add an identity column if the date is unique.
Tim
ASKER
Ok so what i don't understand, (i fixed the relationship). I have the memberNamesUnique property set to false, so why then do i have to associate the primary key, with the column and create the name column? becuase ifi i don't do this, i get anerror when i process the dimension. haven't even started to develop the cube yet