InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comTue, 21 May 2013 06:57:25 GMT20http://www.sqlservercentral.com/Forums/Topic546938-1320-1.aspxIt only outputs indexes that have common first seek columns. Indexes that have common first seek columns are dupes or might be merge-able, or the one of the indexes might be able to get their seek columns rearranged so you can have more index usage possibilities without adding more indexes.I would only intentially have indexes with common first seek columns on tables with hardly any write activity.The only other reason to dupe on first seek columns is to dupe on PKs that experience a lot of multi-row up-stream (from many to one; Where is on the many table) joins that cause bookmark lookups. PKs (also UQ constraints) can't have include columns, so you have to create another nonclustered index that has the seem seek as the PK and then add include columns.Tue, 28 Oct 2008 11:21:46 GMTYeshuaAgapaohttp://www.sqlservercentral.com/Forums/Topic546938-1320-1.aspxI am not sure I understand what is considered a duplicate index. It appears that if more than one index starts with the same field, that it is considered a duplicate index. I have 4 indexes on one table that all have the same field as the first member. Why are these considered duplicate indexes?ThanksGlenMon, 20 Oct 2008 14:16:30 GMTGlen Weldon Maneyhttp://www.sqlservercentral.com/Forums/Topic546938-1320-1.aspxComments posted to this topic are about the item [B]<A HREF="/scripts/Index+Management/63935/">The Ultimate Duplicate Index Finder</A>[/B]Tue, 05 Aug 2008 11:16:15 GMTYeshuaAgapao