http://blogs.msdn.com/ianjo/archive/2006/04/24/582227.aspxA common problem for some SQL Server applications are cases where data typically ascends. For example, datetime columns where the column represents a current date. SQL Server builds statistics with the assumption that the data will by in large be similaren-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/ianjo/archive/2006/04/24/582227.aspx#771413Tue, 26 Sep 2006 03:50:35 GMT91d46819-8472-40ad-a661-2c78acb4018c:771413Tips, Tricks, and Advice from the SQL Server Query Processing TeamSince we’re starting a new blog for the whole query processing team, we think it’s appropriate to start...http://blogs.msdn.com/ianjo/archive/2006/04/24/582227.aspx#822322Fri, 13 Oct 2006 20:02:03 GMT91d46819-8472-40ad-a661-2c78acb4018c:822322nd-pike<p>We have seen this problem on SQL Server 2000 with datetime columns. &nbsp;Are there any plans to add these trace flags in a future hotfix for 2000?</p> http://blogs.msdn.com/ianjo/archive/2006/04/24/582227.aspx#1302323Sat, 16 Dec 2006 09:38:20 GMT91d46819-8472-40ad-a661-2c78acb4018c:1302323JasonMassie<p>I have been running into resource_semaphore_query_compile wait types. After several months of troubleshooting, our workaround is toggling forced paramaterization off/on, freeing the proc cache and updating stats. I am pretty sure that just updating stats would work but freeing the proc cahce provides some immediate temporary relief. </p> <p>The problem happens first thing in the morning when inserts are the highest. I think we may be running into this but will this type on stats updates cause recompiles of procs and parameterized queries?</p>