<?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: General Tips on Optimizing SQL Server Indexes</title>
	<atom:link href="http://www.sql-server-performance.com/2007/optimizing-indexes-general/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sql-server-performance.com/2007/optimizing-indexes-general/</link>
	<description>SQL Server Performance Tuning</description>
	<lastBuildDate>Fri, 17 May 2013 13:31:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Christoph D</title>
		<link>http://www.sql-server-performance.com/2007/optimizing-indexes-general/#comment-362</link>
		<dc:creator>Christoph D</dc:creator>
		<pubDate>Thu, 09 Jun 2011 12:16:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?=207#comment-362</guid>
		<description><![CDATA[Queries that include either the DISTINCT or the GROUP BY clauses can be optimized by including appropriate indexes. Any of the following indexing strategies can be used:
•Include a clustered index on the columns found in the SELECT clause.
*****
This may be correct for nonclustered indexes to be sure that it is a covering index but the leaf-level of a clustered data is always the data of the table itself.
I would highly suggest to put a clustered index, as it was said before, on an increasing unique value if there are many data manipulations on this table or on a column that is queried for a specific range very often (like a date maybe) if there are many selects on this range to improve performance for these queries.]]></description>
		<content:encoded><![CDATA[<p>Queries that include either the DISTINCT or the GROUP BY clauses can be optimized by including appropriate indexes. Any of the following indexing strategies can be used:<br />
•Include a clustered index on the columns found in the SELECT clause.<br />
*****<br />
This may be correct for nonclustered indexes to be sure that it is a covering index but the leaf-level of a clustered data is always the data of the table itself.<br />
I would highly suggest to put a clustered index, as it was said before, on an increasing unique value if there are many data manipulations on this table or on a column that is queried for a specific range very often (like a date maybe) if there are many selects on this range to improve performance for these queries.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
