Unable to create index because of duplicate that doesn't exist?

Sql Server-2005TsqlIndexingUnique Index

Sql Server-2005 Problem Overview


I'm getting an error running the following Transact-SQL command:

CREATE UNIQUE NONCLUSTERED INDEX IX_TopicShortName
ON DimMeasureTopic(TopicShortName)

The error is:

> Msg 1505, Level 16, State 1, Line 1 > The CREATE UNIQUE INDEX statement > terminated because a duplicate key was > found for the object name > 'dbo.DimMeasureTopic' and the index > name 'IX_TopicShortName'. The > duplicate key value is ().

When I run SELECT * FROM sys.indexes WHERE name = 'IX_TopicShortName' or SELECT * FROM sys.indexes WHERE object_id = OBJECT_ID(N'[dbo].[DimMeasureTopic]') the IX_TopicShortName index does not display. So there doesn't appear to be a duplicate.

I have the same schema in another database and can create the index without issues there. Any ideas why it won't create here?

Sql Server-2005 Solutions


Solution 1 - Sql Server-2005

It's not that the index already exists, but that there are duplicate values of the TopicShortName field in the table itself. According to the error message the duplicate value is an empty string (it might just be a facet of posting I guess). Such duplicates prevent the creation of a UNIQUE index.

You could run a query to confirm that you have a duplicate:

SELECT
    TopicShortName,
    COUNT(*)
FROM
    DimMeasureTopic
GROUP BY
    TopicShortName
HAVING
    COUNT(*) > 1

Presumably in the other database the data are different, and the duplicates are not present.

Solution 2 - Sql Server-2005

The duplicate is in your data, try running this query to find it.

SELECT TopicShortName, COUNT(*)
FROM DimMeasureTopic
GROUP BY TopicShortName
HAVING COUNT(*) > 1

Solution 3 - Sql Server-2005

It's because you have records in the table already that are not unique (by the sounds of it, 2 records with a blank value in the TopicShortName field).

So, it's to do with the data, not the index itself.

Solution 4 - Sql Server-2005

If you are using code-based migrations, and you rename a property of an entity and you are having an unique index for the property, entity framework will create a new column and trying to add an unique index for the new column but the new column has all null values, therefore it will fail. You need to manually modify the migration code to copy the data from old column before the line to create index.

Solution 5 - Sql Server-2005

It should have specified the duplicate key value in the error message. "The duplicate key value is (' ', ' ', ' ') The statement has been terminated. You have duplicate values that need to be addressed.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionAlex AngasView Question on Stackoverflow
Solution 1 - Sql Server-2005martin claytonView Answer on Stackoverflow
Solution 2 - Sql Server-2005Donald ByrdView Answer on Stackoverflow
Solution 3 - Sql Server-2005AdaTheDevView Answer on Stackoverflow
Solution 4 - Sql Server-2005Ming LuView Answer on Stackoverflow
Solution 5 - Sql Server-2005DBAView Answer on Stackoverflow