<?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>UPDATE STATISTICS undocumented options</title><link>http://blogs.msdn.com/queryoptteam/archive/2006/07/21/674350.aspx</link><description>If you read the Books Online page describing the UPDATE STATISTICS command, you will see that there are some undocumented options. UPDATE STATISTICS table | view [ { { index | statistics_name } | ( { index |statistics_name } [ ,...n ] ) } ] [ WITH [ [</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: UPDATE STATISTICS undocumented options</title><link>http://blogs.msdn.com/queryoptteam/archive/2006/07/21/674350.aspx#677717</link><pubDate>Tue, 25 Jul 2006 12:00:33 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:677717</guid><dc:creator>Wesley Backelant</dc:creator><description>These kind of posts are exactly why I love blogs. &amp;nbsp;This could save us hours of data generation effort. &amp;nbsp;Most of the DBA's here tend to 'forget' testing with a realistic amount of data. &lt;BR&gt;&lt;BR&gt;DTA (ITW) also allows you to fool SQL Server into having more rows, is this based on the same principle?</description></item><item><title>re: UPDATE STATISTICS undocumented options</title><link>http://blogs.msdn.com/queryoptteam/archive/2006/07/21/674350.aspx#678613</link><pubDate>Wed, 26 Jul 2006 07:30:45 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:678613</guid><dc:creator>QueryOptTeam</dc:creator><description>Hi Wesley - thank you for the interest and feedback.
&lt;br&gt;
&lt;br&gt;I believe that DTA uses these same interfaces, but am not 100% sure.
&lt;br&gt;
&lt;br&gt;About testing with realistic amounts of data: i want to be perfectly clear about the fact that UPDATE STATISTICS WITH ROWCOUNT and PAGECOUNT will only fool the Optimizer into believing that the table is actually bigger (or smaller for that matter) than in reality. However, the content of the actual tables and indexes will remain perfectly intact. So while it is true that these commands will let you see what kind of query plans the Optimizer would generate against larger amounts of data, actually running these plans would not provide particularly interesting information. All query plans will complete extremely quickly when run against empty or very small tables.
&lt;br&gt;
&lt;br&gt;What you can do, however, is to look at the progression of the estimated query cost based on the size of the tables. If the cost grows significantly with the size – i.e. the query performances do not seem to scale with the amount of data - it might be a hint that maybe some tuning is required.
&lt;br&gt;
&lt;br&gt;Stefano</description></item><item><title>re: UPDATE STATISTICS undocumented options</title><link>http://blogs.msdn.com/queryoptteam/archive/2006/07/21/674350.aspx#678676</link><pubDate>Wed, 26 Jul 2006 09:29:45 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:678676</guid><dc:creator>Wesley Backelant</dc:creator><description>Thanks for the extra explanation.
&lt;br&gt;
&lt;br&gt;I do understand that nothing can compete with realistic data. &amp;nbsp;But I'd rather see people try some first optimizations with artificial statistics than not optimizing at all because they have no time to generate test data, especially since I'm typically the one who has to solve it once it goes to production :-)
&lt;br&gt;
&lt;br&gt;I still love the black art of query tuning though ;-)
&lt;br&gt;
&lt;br&gt;Wesley</description></item><item><title>re: UPDATE STATISTICS undocumented options</title><link>http://blogs.msdn.com/queryoptteam/archive/2006/07/21/674350.aspx#683614</link><pubDate>Mon, 31 Jul 2006 04:24:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:683614</guid><dc:creator>mz1313</dc:creator><description>Thank you for this post! It came exectly at time, while I was breaking my head trying to simulate behavior of a table with 70 Gb of data without actually loading it. &lt;BR&gt;My question is - is there any way to fool Full-Text index? When I created Full-Text index on my table and executed query with CONTAINS(...), the "Estimated Row Count" in the execution plan was again 1 instead of 3M estimated row count in the query without CONTAINS(...).</description></item><item><title>re: UPDATE STATISTICS undocumented options</title><link>http://blogs.msdn.com/queryoptteam/archive/2006/07/21/674350.aspx#684322</link><pubDate>Mon, 31 Jul 2006 21:02:10 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:684322</guid><dc:creator>QueryOptTeam</dc:creator><description>Unfortunately, at the moment there is no way to change the statistics for internal hidden tables like those used for Full Text Search. This is a limitation we should definitely attempt to remove in some future release.
&lt;br&gt;
&lt;br&gt;Thanks you for the great feedback!
&lt;br&gt;Stefano</description></item><item><title>dosql   ::  Used update statistics on DEV env to get the PRD execution plan</title><link>http://blogs.msdn.com/queryoptteam/archive/2006/07/21/674350.aspx#1179556</link><pubDate>Fri, 01 Dec 2006 00:45:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1179556</guid><dc:creator>dosql   ::  Used update statistics on DEV env to get the PRD execution plan</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.dosql.com/blog/?p=87"&gt;http://www.dosql.com/blog/?p=87&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>update statistics undocumented</title><link>http://blogs.msdn.com/queryoptteam/archive/2006/07/21/674350.aspx#1844406</link><pubDate>Fri, 09 Mar 2007 16:59:04 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1844406</guid><dc:creator>roy ashbrook</dc:creator><description>&lt;p&gt;these are undocumented for a reason as they will affect performance and you will break your sql production&lt;/p&gt;
</description></item><item><title>How to create fake statistics for testing query plans</title><link>http://blogs.msdn.com/queryoptteam/archive/2006/07/21/674350.aspx#1869046</link><pubDate>Tue, 13 Mar 2007 04:49:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1869046</guid><dc:creator>SQL Server Storage Engine</dc:creator><description>&lt;p&gt;This is very cool - an undocumented option to UPDATE STATISTICS that allows you to fool the server into&lt;/p&gt;
</description></item><item><title>Online Indexing operations enhancement in SQL Server 2005</title><link>http://blogs.msdn.com/queryoptteam/archive/2006/07/21/674350.aspx#1901334</link><pubDate>Sat, 17 Mar 2007 21:35:18 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1901334</guid><dc:creator>SQL Server tools</dc:creator><description>&lt;p&gt;In SQL Server designing efficient indexes is paramount to achieving good database and application performance.&lt;/p&gt;
</description></item><item><title> Tips Tricks and Advice from the SQL Server Query Optimization Team | Quick Diets</title><link>http://blogs.msdn.com/queryoptteam/archive/2006/07/21/674350.aspx#9722594</link><pubDate>Wed, 10 Jun 2009 06:13:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9722594</guid><dc:creator> Tips Tricks and Advice from the SQL Server Query Optimization Team | Quick Diets</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://quickdietsite.info/story.php?id=4048"&gt;http://quickdietsite.info/story.php?id=4048&lt;/a&gt;&lt;/p&gt;
</description></item><item><title> Tips Tricks and Advice from the SQL Server Query Optimization Team | debt settlement program</title><link>http://blogs.msdn.com/queryoptteam/archive/2006/07/21/674350.aspx#9753888</link><pubDate>Mon, 15 Jun 2009 20:02:22 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9753888</guid><dc:creator> Tips Tricks and Advice from the SQL Server Query Optimization Team | debt settlement program</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://edebtsettlementprogram.info/story.php?id=24748"&gt;http://edebtsettlementprogram.info/story.php?id=24748&lt;/a&gt;&lt;/p&gt;
</description></item><item><title> Tips Tricks and Advice from the SQL Server Query Optimization Team | storage bench</title><link>http://blogs.msdn.com/queryoptteam/archive/2006/07/21/674350.aspx#9782589</link><pubDate>Fri, 19 Jun 2009 11:03:26 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9782589</guid><dc:creator> Tips Tricks and Advice from the SQL Server Query Optimization Team | storage bench</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://thestoragebench.info/story.php?id=9514"&gt;http://thestoragebench.info/story.php?id=9514&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>