http://blogs.msdn.com/sqltips/archive/tags/Performance+-+Tools/default.aspxTags: Performance - Toolsen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/sqltips/archive/2006/02/14/532258.aspxWed, 15 Feb 2006 05:58:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:532258SQL Server Engine Team3http://blogs.msdn.com/sqltips/comments/532258.aspxhttp://blogs.msdn.com/sqltips/commentrss.aspx?PostID=532258http://blogs.msdn.com/sqltips/rsscomments.aspx?PostID=532258<DIV>Index Tuning Wizard (ITW in SQL Server 2000) or Database Engine Tuning Advisor (DTA in SQL Server 2005) allow you to analyze a workload and make recommendations for the database based on the workload. The recommendations are schema changes, partitioning or indexed view creation for example. During the recommendation process, ITW or DTA can create hypothetical indexes or statistics it will use to analyze the workload. Creation of these indexes or statistics on any table increments the schema version information that is maintained by the database engine. As a result of this, any subsequent queries that reference tables that were touched by ITW or DTA will result in recompilation. This recompilation will be at the statement level in SQL Server 2005 or at the stored procedure level in SQL Server 2000. This is something that you should watch out for when trying to use ITW or DTA on a production machine directly. It is always better to run the tool on a copy of the production database on a different machine in isolation so you can review the changes without affecting other workload and also apply the changes easily without interruption.</DIV> <DIV>&nbsp;</DIV> <DIV>--</DIV> <DIV>Umachandar</DIV><img src="http://blogs.msdn.com/aggbug.aspx?PostID=532258" width="1" height="1">Performance - Toolshttp://blogs.msdn.com/sqltips/archive/2006/02/14/532169.aspxWed, 15 Feb 2006 02:46:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:532169SQL Server Engine Team1http://blogs.msdn.com/sqltips/comments/532169.aspxhttp://blogs.msdn.com/sqltips/commentrss.aspx?PostID=532169http://blogs.msdn.com/sqltips/rsscomments.aspx?PostID=532169<DIV>Did you know that SQL Server 2005 adds a new trace flag (-T1222) for deadlock trace output? This deadlock output has numerous improvements over older versions of SQL Server. For example, some of the enhancements of the new grace flag are:</DIV> <DIV>&nbsp;</DIV> <DIV>1. XML like&nbsp;output for the deadlock</DIV> <DIV>2. Execution stack at the time of the deadlock</DIV> <DIV>3. Log space used by the task(s) involved in the deadlock</DIV> <DIV>&nbsp;</DIV> <DIV>For more details, see the Books Online topic: <A href="http://msdn2.microsoft.com/en-us/library/ms178104(SQL.90).aspx">Detecting and Ending Deadlocks</A>.</DIV> <DIV>&nbsp;</DIV> <DIV>Additionally, you can also view a graphical representation of the deadlock using the SQL Server 2005 Profiler tool now. You can find out more about this from the Books Online topic: <A href="http://msdn2.microsoft.com/en-us/library/ms188246.aspx">Analyzing Deadlocks with SQL Server Profiler</A>.</DIV> <DIV>&nbsp;</DIV> <DIV>--</DIV> <DIV>Umachandar</DIV> <DIV>&nbsp;</DIV><img src="http://blogs.msdn.com/aggbug.aspx?PostID=532169" width="1" height="1">Performance TroubleshootingPerformance - Tools