Can't Kill SPID

  • We have a very persistent record in our SQL 2000 server. When I query the sysprocesses table for a specific SPID (7), I get the attached result.

    When I try to kill it, I get this message:

    Msg 6107, Level 14, State 1, Line 1

    Only user processes can be killed.

    What is going on? This has blocked SPID 56 for a long time, and I don't know what I ned to do to make it stop. Can someone please help out?

    Thanks.

    Steve

  • Exactly as the error says, you can't kill system processes and 7 is a system process.

    What's it doing? Does it have a wait type?

    What's session 56 doing? What's its wait type?

    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

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Per the txt file he attached, it's a LATCH_EX wait (0x404), and the host process is Task Manager.

    Doesn't tell us much, but it says it's code waiting to execute, not a buffer latch or anything like that.

    So, I'd look for things like a long-running job, or some external DLL doing something funky in the SQL space.

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • Sorry, didn't notice the attachment.

    That says very little. Latch waits are waits memory structures and without info on what memory structure (which, iirc SQL 2000 does not expose) it's going to be hard to diagnose further.

    Could be that some other process (user most likely) holds the latch that the system process is waiting for (however that's not exposed either).

    Worst case, restart SQL. But that's a last resort.

    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

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

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

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