Tempdb CPUTime

  • Hi all -

    I was receiving complaints about how an application was running slowly. When I did a sp_who2 to help diagnose the problem, I saw that a process in the tempdb had a very, very high CPUTime. Any ideas what could cause this? I'm at a lost, since the process came from my machine and I had nothing running. I'm wondering if something got "stuck." Any help with this would be greatly appreciated. Thanks!

    PS: This is on a Windows 2003/SQL 2005 box.

  • Whats the service pack you have on your server?

  • Are you sure it is the database server acting slowly and not the application or OS hosting the app itself? You can run a profile trace to find out what's going on the server to help determine execution times of activity on the database to help diagnose the problem.

    I would think running perfmon on the SQL server and host running the app would help identify performance issues of subsystems such as disk or CPU as well.

    Joie Andrew
    "Since 1982"

  • I'm running SP2.

    And once I killed the process in question, the application speed returned to normal.

  • Does your machine host any scripts that could have been running at that time? If it happens again can you check in Activity Monitor the user logged against that activity? Then you could run a trace filtered by that user and get an idea of what activity is going on.

    Joie Andrew
    "Since 1982"

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

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