Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

Unable to Kill Process :dbcc inputbuffer Expand / Collapse
Posted Monday, June 14, 2010 9:27 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, June 24, 2010 7:21 PM
Points: 8, Visits: 24

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.

Post #937229
Posted Monday, April 7, 2014 8:59 AM



Group: Administrators
Last Login: Yesterday @ 2:36 PM
Points: 33,052, Visits: 17,302
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.

Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1559129
Posted Monday, April 7, 2014 9:02 AM



Group: General Forum Members
Last Login: Today @ 1:23 AM
Points: 44,014, Visits: 41,418
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

Post #1559131
Posted Monday, April 7, 2014 12:57 PM



Group: General Forum Members
Last Login: 2 days ago @ 4:52 PM
Points: 22,580, Visits: 35,879
Almost a four year old thread.

Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
Post #1559232
Posted Monday, April 7, 2014 1:32 PM



Group: General Forum Members
Last Login: Yesterday @ 5:19 PM
Points: 39,691, Visits: 36,829
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."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Favorite Quotes:
"Has anyone ever told you that a query you have written runs too fast?" - Dwain Camps - 6 Mar 2014

Helpful Links:
How to post code problems
How to post performance problems
Post #1559248
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse