<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqladvice.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>Creating Covering Indexes - That much easier with SS 2005</title><link>http://sqladvice.com/blogs/repeatableread/archive/2006/06/13/18650.aspx</link><description>Index Tuning is something that I _really_ enjoy - mostly because I just love seeing performance improvements. It's always exciting to see tangible improvements in existing systems. Recently while looking into a query that was causing a lot of reads for</description><dc:language>en</dc:language><generator>CommunityServer 2.1 (Build: 60809.935)</generator><item><title>re: Creating Covering Indexes - That much easier with SS 2005</title><link>http://sqladvice.com/blogs/repeatableread/archive/2006/06/13/18650.aspx#26093</link><pubDate>Wed, 10 Jan 2007 05:08:48 GMT</pubDate><guid isPermaLink="false">81c49694-04ec-4285-ae1c-61808dc1a845:26093</guid><dc:creator>dmarkle</dc:creator><description>&lt;p&gt;SS 2005 definitely is nicer. &amp;nbsp;Another thing to mention as well would be its new &amp;quot;included columns&amp;quot; feature, which saves you from some of the overhead of maintaining lower-order index keys just to include them in the query output.&lt;/p&gt;
</description></item></channel></rss>