<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>SQL Server Statistics</title><link>http://blogs.technet.com/rob/archive/2008/05/16/sql-server-statistics.aspx</link><description>SQL Server 2005 collects statistical information about indexes and column data stored in the database. These statistics are used by the SQL Server query optimizer to choose the most efficient plan for retrieving or updating data. Good statistics allow</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Rob's SQL Server Blog : SQL Server Statistics</title><link>http://blogs.technet.com/rob/archive/2008/05/16/sql-server-statistics.aspx#3058581</link><pubDate>Wed, 21 May 2008 15:57:01 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3058581</guid><dc:creator>Rob's SQL Server Blog : SQL Server Statistics</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://blogs.technet.com/rob/archive/2008/05/16/sql-server-statistics.aspx"&gt;http://blogs.technet.com/rob/archive/2008/05/16/sql-server-statistics.aspx&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>SQL Server Statistics</title><link>http://blogs.technet.com/rob/archive/2008/05/16/sql-server-statistics.aspx#3058587</link><pubDate>Wed, 21 May 2008 15:59:38 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3058587</guid><dc:creator>Other SQL Server Blogs around the Web</dc:creator><description>&lt;p&gt;SQL Server 2005 collects statistical information about indexes and column data stored in the database&lt;/p&gt;
</description></item><item><title>re: SQL Server Statistics</title><link>http://blogs.technet.com/rob/archive/2008/05/16/sql-server-statistics.aspx#3134086</link><pubDate>Wed, 08 Oct 2008 17:01:25 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3134086</guid><dc:creator>charlie</dc:creator><description>&lt;p&gt;do you know why you can't delete the auto statistics from management studio?&lt;/p&gt;</description></item><item><title>re: SQL Server Statistics</title><link>http://blogs.technet.com/rob/archive/2008/05/16/sql-server-statistics.aspx#3134242</link><pubDate>Wed, 08 Oct 2008 23:03:40 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3134242</guid><dc:creator>robcarrol</dc:creator><description>&lt;p&gt;You need to delete the auto-created statistics using a DROP STATISTICS statement. However, you can delete manually created statistics through the Management Studio GUI.&lt;/p&gt;
</description></item><item><title>re: SQL Server Statistics</title><link>http://blogs.technet.com/rob/archive/2008/05/16/sql-server-statistics.aspx#3137848</link><pubDate>Fri, 17 Oct 2008 16:37:27 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3137848</guid><dc:creator>Michelle</dc:creator><description>&lt;P&gt;If you create a new index is it advisable to drop system created indexes for those columns. &amp;nbsp;Any issues?&lt;/P&gt;</description></item><item><title>re: SQL Server Statistics</title><link>http://blogs.technet.com/rob/archive/2008/05/16/sql-server-statistics.aspx#3141821</link><pubDate>Sat, 25 Oct 2008 13:58:14 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3141821</guid><dc:creator>robcarrol</dc:creator><description>&lt;p&gt;Hi Michelle. Are you referring to indexes created by the Database Tuning Advisor? It is not a good idea to have duplicate indexes on the same columns in a table. Duplicate indexes provide no performance or manageability benefits. &lt;/p&gt;
&lt;p&gt;Each duplicate index increases the I/O overhead of insert, update, and delete operations, as well as index rebuilds and index reorganizations. The overall result is reduced performance, longer maintenaince times and increased disk space usage. Dropping the duplicate indexes can provide an immediate performance benefit for data modifications and index maintainance. Existing queries that reference the index will continue to use the original, non-duplicated index. &lt;/p&gt;
&lt;p&gt;Before dropping, ensure that no applications explicitly reference the duplicate indexes as this will cause errors after you delete it. Also, script out the duplicate index in Microsoft SQL Server Management Studio in case you need to recreate it again. After scripting the index, issue a DROP INDEX command against the duplicate index in order to remove it from the database.&lt;/p&gt;
</description></item></channel></rss>