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 ( 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: Microsoft SQL Performance Troubleshooting Guidance: Patrick LeBlanc's article on using WildCard Filter SQL Server Central Forums discussion on trace creating CPU and Thread waits:

No comments:

Post a Comment