<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Detecting Overlapping Indexes in SQL Server 2005</title><link>http://blogs.msdn.com/mssqlisv/archive/2007/06/29/detecting-overlapping-indexes-in-sql-server-2005.aspx</link><description>When SQL Server has an optimal index that satisfies the search predicates of a query the optimizer performs an index SEEK operation as opposed to an index (or table) scan to retrieve the required rows; this is desirable. Based on this, one may be led</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Index Overlaps</title><link>http://blogs.msdn.com/mssqlisv/archive/2007/06/29/detecting-overlapping-indexes-in-sql-server-2005.aspx#4496760</link><pubDate>Tue, 21 Aug 2007 20:37:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:4496760</guid><dc:creator>Carpe Datum</dc:creator><description>&lt;p&gt;There are a lot of tools in SQL Server 2005 that will help you with indexes, from enhanced plan diagrams&lt;/p&gt;
</description></item><item><title>Covering Clustered Indexes</title><link>http://blogs.msdn.com/mssqlisv/archive/2007/06/29/detecting-overlapping-indexes-in-sql-server-2005.aspx#8552395</link><pubDate>Mon, 26 May 2008 16:28:13 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8552395</guid><dc:creator>Grumpy Old DBA</dc:creator><description>&lt;p&gt;I’ve noticed that of late I’ve become a bit more critical of a well known publication that I suspect&lt;/p&gt;
</description></item></channel></rss>