<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Tips on Optimizing SQL Server Composite Indexes</title>
	<atom:link href="http://www.sql-server-performance.com/2007/composite-indexes/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sql-server-performance.com/2007/composite-indexes/</link>
	<description>SQL Server Performance Tuning</description>
	<lastBuildDate>Fri, 14 Jun 2013 19:09:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Darton Williams</title>
		<link>http://www.sql-server-performance.com/2007/composite-indexes/#comment-1910</link>
		<dc:creator>Darton Williams</dc:creator>
		<pubDate>Thu, 10 May 2012 14:51:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?=209#comment-1910</guid>
		<description><![CDATA[I&#039;ve found that correct composite indexes can make a huge difference in performance when joining multiple tables and filtering on several columns. I have a query joining three tables, two of which contain only foreign keys. The largest one has ~32000 rows, so not a huge database.
This query, returning 600 rows, took over 7 minutes to run when I first began testing. The execution plan did not show any table scans and all single-key indexes were being used. Rewriting the query helped, but it still took minutes. Adding two composite indexes on each foreign key table decreased execution time to &lt; 1 second.
Strangely, the execution plan did not show much of a change in relative time spent on the formerly slow join to the rest of the query.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve found that correct composite indexes can make a huge difference in performance when joining multiple tables and filtering on several columns. I have a query joining three tables, two of which contain only foreign keys. The largest one has ~32000 rows, so not a huge database.</p>
<p>This query, returning 600 rows, took over 7 minutes to run when I first began testing. The execution plan did not show any table scans and all single-key indexes were being used. Rewriting the query helped, but it still took minutes. Adding two composite indexes on each foreign key table decreased execution time to &lt; 1 second. </p>
<p>Strangely, the execution plan did not show much of a change in relative time spent on the formerly slow join to the rest of the query.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
