Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

sp_who2 active report help Expand / Collapse
Author
Message
Posted Wednesday, May 7, 2014 12:02 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, November 21, 2014 9:06 AM
Points: 124, Visits: 451
I was having 'Slowness' on App server. when I ran 'SP_who2 active' ON DATABASE server found these:

spid: 12
status: background,
login: SA,
DBName: 'ProdDB',
Command: 'Checkpoint',
CPU time 2566666,
Disk IO 172232,
Last Batch '8 days ago'.

Can you guys tell me if that is an issue, if so where should I start from??? Help Plz.
Post #1568634
Posted Wednesday, May 7, 2014 12:38 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 11:01 AM
Points: 14,029, Visits: 28,404
That's an internal process. It's not the cause of your issue. I'd suggest you look for blocked or blocking processes or non-system processes. Also, generally, I don't suggest using sp_who or sp_who2. Instead run queries against sys.dm_exec_requests and the associated dynamic management views. You can get a lot more detail on long running or blocked/blocking processes that way.

----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server Query Performance Tuning
SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1568651
Posted Wednesday, May 7, 2014 1:32 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, November 21, 2014 9:06 AM
Points: 124, Visits: 451
Thanks for your reply. My concern is why it's say Proddb, and checkpoint, lot of cpu and IO and it's sitting there since last 6 days, should I be concern?

DBName: 'ProdDB',
Command: 'Checkpoint',
CPU time 2566666,
Disk IO 172232,
Last Batch 'May 6, 2014'.
Post #1568672
Posted Wednesday, May 7, 2014 2:46 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 11:01 AM
Points: 14,029, Visits: 28,404
Last batch means the last time it was run, not the amount of time it's been running.

It's the checkpoint operation. That's a fundamental part of the process. It's actually what gets things written from memory to disk within SQL Server.


----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server Query Performance Tuning
SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1568695
Posted Thursday, May 8, 2014 4:15 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, November 21, 2014 9:06 AM
Points: 124, Visits: 451
yes, you're write about last batch. Thank you
Post #1569106
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse