November 1, 2004 at 2:16 am
I have been told that monitoring locks using SQL Profiler is prohibitively expensive in terms of resources though using the tool to monitor other activity isn't a problem.
This seems a bit suspicious to me but is it correct?
November 1, 2004 at 9:33 am
Using profiler to do anything but spot check problems isn't recommended. Setup a server side trace if it is something you want to track over time. Profiler can consume as much as 15% of your server resources.
Wes
November 2, 2004 at 9:38 am
The profiler graphic interface is very resource-intensive, so you can take some of the load off the server by running profiler on another computer.
Another question would be what you mean by "monitoring locks". It might be reasonable to look for Deadlock or Timeout events, but tracing every Acquired and Released event would really slow it down.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply