Exception on multiple indexes with identical name

• 
  Hi Florian,
  
  Thanks for contacting Red Gate. From my experience, system-generated index names contain a random string of numbers in the name to try to keep them unique. SQL Server should not allow identically-named objects (unless the database is case-sensitive and/or the object name is owned by a different schema).
  
  Can you tell us what version of Dependency Tracker is doing this, and what objects were added that caused the error?

  Brian Donahue July 18, 2014 11:46

  - 0 +
• 
  Hey Brian,
  
  to be honest, I am not sure, how these indexes got there, but they don't contain anything random and are all owned by the same schema. We turned off automatic index generation a long time ago, but it seems like some are still around. Could have been some old performance tool that made this poor name choice as well. Anyway - since this is in production I am not going to be able to get rid of those in the short term.
  
  I did some digging and it turns out, Microsoft actually does allow multiple indexes with identical names, as long as they are not created on the same object:

  index_name
  Is the name of the index. Index names must be unique within a table or view but do not have to be unique within a database. Index names must follow the rules of identifiers.

  See http://msdn.microsoft.com/en-us/library ... (v=sql.105).aspx
  
  I am using Dependecy Tracker Version 2.8.1.164, which I downloaded just yesterday as part of the SQL Developer Bundle.
  
  -- Florian

  florian kistner July 18, 2014 12:07

  - 0 +
• 
  Thanks for pointing this out. I did create a representative sample of a set of tables with an index that is identically-named, and Dependency Tracker was able to add the objects to the view.

  CREATE TABLE [23456] (
  id int PRIMARY KEY,
  col1 CHAR(10)
  )
  CREATE TABLE [34567] (
  id INT PRIMARY KEY,
  col2 CHAR(10)
  )
  CREATE INDEX [_MY_INDEX] ON [23456] (col1);
  CREATE INDEX [_MY_INDEX] ON [34567] (col2)
  

  
  I'll send you some debugging instructions via email, because we probably need some more information about this schema.

  Brian Donahue July 21, 2014 04:27

  - 0 +
• 
  Has anybody else experienced this problems? If so, what is the solution to get the dependency diagrams working for SQL Server 2012 (it seems to work fine for SQL Server 2008 databases though)? ???

  Aliraza70 April 07, 2015 04:56

  - 0 +

Add comment

Please sign in to leave a comment.