September 7, 2006 at 10:04 am
SQL 2005 SP1 on Windows Server 2003
Just moved to 2005 from 2000 and scaling the learning curve! An oddity - when running Profiler from a workstation, the CPU utilisation on the server drops almost to zero and the users complain that the system is running slowly. Stop the trace, CPU comes up to 40-50% and the users are happy again.
Any idea what is going on?
First time I've ever complained that the CPU wasn't busy enough...
--
Scott
September 8, 2006 at 9:00 am
Make sure to choose as fewer events as possible. Too many events tracing, expecially those for performance (show plan etc.), generates a large volumn of network traffic that could prevent users to connect to your server. Saving the trace result to local disk is a better way.
Regards,
Jin
September 8, 2006 at 9:02 am
the only time I ever saw something like this was due to the thread starvation.
Run this DBCC SQLPERF (UMSSTATS) while your profiler is running and see if work queued is > 0
September 11, 2006 at 10:19 am
We have the same problem when some of my developers insist on using their debugging tools in production.
The locks start blocking transactions, and the CPU goes down to almost nothing.....and the users start timing out.
Eric
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply