January 24, 2012 at 10:46 am
We are seeing 100% CPU utilization on one of our SQL servers for the process sqlsevr.exe. I ran an sp_who2 query and discovered the LOG WRITER command taking ten times the CPU time as any other command. What can I do to address this? This particular server has two CPUs and 8 GB of RAM.
Thanks in advance for the usual helpful response.
Cheers
Tom
January 24, 2012 at 11:23 am
Bear in mind that the CPU returned by sp_who2 is cumulative since that connection was established. If you're looking at one of the system processes, it would have been running since SQL Server started and could have a very high cumulative CPU.
One look at that DMV is not usually useful, a connection that's been established for a couple of days with a CPU value of 200000 is probably less of a concern than one that's been established a couple minutes with a CPU value of 1200.
Also, chapter 3 of http://www.simple-talk.com/books/sql-books/troubleshooting-sql-server-a-guide-for-the-accidental-dba/
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply