Monday, October 5, 2009

SQL Profiler can be a dangerous tool

Left unchecked SQL Profiler can be a dangerous tool. There are some conditions where a trace that has worked safely in the past can wreak havoc on a production server.

FIX: CPU utilization is high when you run a trace that contains a text filter in SQL Server 2005 (http://support.microsoft.com/kb/953496) Note: sometimes I find that Microsoft fixes don't always completely resolve an issue. This can simply happen because the cause of the issue is not well understood. I like to consider them even if the fix is in place. Microsoft guidance on using Profiler: http://support.microsoft.com/kb/224587/ Microsoft SQL Performance Troubleshooting Guidance: http://support.microsoft.com/kb/298475 Patrick LeBlanc's article on using WildCard Filter http://www.sqlservercentral.com/blogs/sqldownsouth/archive/2009/08/21/sql-profiler-wild-card-filter-on-textdata.aspx SQL Server Central Forums discussion on trace creating CPU and Thread waits: http://www.sqlservercentral.com/Forums/Topic765171-360-1.aspx

No comments:

Post a Comment