Prev: CacheHitRatio
Next: find a certain table from sql server
From: Derek on 7 Apr 2010 11:50
I need help interpreting the following sp_who2 output. I'm not sure
if this is a problem or not.


SPID Status Command CPUTime
DiskIO LastBatch
1 BACKGROUND RESOURCE MONITOR 45004812 17967 03/11
09:03:05
2 BACKGROUND LAZY WRITER 656562 0 03/11
09:03:05
3 SUSPENDED LOG WRITER 27216453 0
03/11 09:03:05
10 BACKGROUND CHECKPOINT 7527140 3612872 03/11
09:03:05

I see high CPU and large disk for checkpoint.... are these values
causes for concern?
From: Andrew J. Kelly on 7 Apr 2010 16:31
Usually not. These numbers for CPU, I/O etc are since the session was first
started. In this case probably the last time SQL Server was restarted. So a
high number by itself is meaningless, you need a reference of how long its
been running. And checkpoints naturally do a lot of I/O etc. Basically be
more concerned with SPID's higher than 50 because the ones lower are system
spids.

--

Andrew J. Kelly SQL MVP
Solid Quality Mentors

"Derek" <gepetto_2000(a)yahoo.com> wrote in message
news:b18ad581-d0f9-4ffa-b5e8-8b95ec4410c6(a)g10g2000yqh.googlegroups.com...
> I need help interpreting the following sp_who2 output. I'm not sure
> if this is a problem or not.
>
>
> SPID Status Command CPUTime
> DiskIO LastBatch
> 1 BACKGROUND RESOURCE MONITOR 45004812 17967 03/11
> 09:03:05
> 2 BACKGROUND LAZY WRITER 656562 0 03/11
> 09:03:05
> 3 SUSPENDED LOG WRITER 27216453 0
> 03/11 09:03:05
> 10 BACKGROUND CHECKPOINT 7527140 3612872 03/11
> 09:03:05
>
> I see high CPU and large disk for checkpoint.... are these values
> causes for concern?

 | 
Pages: 1
Prev: CacheHitRatio
Next: find a certain table from sql server