sp_who2 active report help

  • 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.

  • 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

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • 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'.

  • 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

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • yes, you're write about last batch. Thank you

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply