Post reply

Unable to Kill Process :dbcc inputbuffer

  • June 14, 2010 at 9:27 pm

    #103948

    Hi,

    Trying to kill this process using kill 14 but does not

    work. dbcc inputbuffer(14) shows the following.

    How can I force to kill this process which has run a few

    days ago on NT4 using MSSQL 7.0?

    I am supposed to restore a database but it prompts me that the database is currently in used. I did check the processes currently running and it show that SPID 14 is runnable. This is the reason why Im trying to Kill the Process.

    Please advise. Thank you.

  • April 7, 2014 at 8:59 am

    #1703831

    There's no "following" that explains what you see.

    However likely if you can't kill the process, you'll need to restart SQL Server.

  • April 7, 2014 at 9:02 am

    #1703833

    You can't kill system processes, and from the value of the spid, that's likely a system process.

    Why do you want to kill it?

    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

  • April 7, 2014 at 12:57 pm

    #1703922

    Almost a four year old thread.

  • April 7, 2014 at 1:32 pm

    #1703935

    Lynn Pettis (4/7/2014)

    Almost a four year old thread.

    BWAAA-HAAAA!!! (Sorry... did that come out loud?) 😛

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

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

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