SQLServerCentral / Article Discussions / Article Discussions by Author / Discuss content posted by Chris / Waiting on a KILL / Latest Posts

RE: Waiting on a KILL

L' Eomot Inversé — Tue, 07 Dec 2010 10:47:04 GMT

[quote][b]OCTom (12/1/2008)[/b][hr]The article referenced is no longer valid. A more up-to-date answer would be appreciated. It seems to me that what was listed as the correct answer and the roll back answer are equalkly valid and neither is the "best" answer.:unsure:[/quote]Although the article is out of date, it still correctly lists things that can cause kill to take a very long time. Scripts in an article that originated more than 7 years ago can be expected to need some updating/revision (pretty drastic revieion, even) but that doesn't invalidate the useful information content.

RE: Waiting on a KILL

L' Eomot Inversé — Tue, 07 Dec 2010 10:44:26 GMT

[quote][b]Chris Harshman (12/1/2008)[/b][hr]I thought the only thing that prevented a KILL from working was if the session was calling an extended stored procedure, was the same session that issued the KILL, or you tried to kill a system session?[/quote]Some things prevent it from working quickly: rollback can take a long time, and the killed process will not die until rollback is complete; if the process is waiting on a write to the client, it isn't executing any code so it can't look to see that its kill flag has been set and won't die until it comes out of the wait; any other synchronous IO that it's waiting for can have the same effect; and MSSQL may still have some bugs (code paths that should check the kill flag but don't) but that would surprise me. If network connections have been set up with ridiculously long timeout the IO waits can seem to last for ever, so that KILL effectively doesn't work.

RE: Waiting on a KILL

Jamie Longstreet-481950 — Tue, 02 Dec 2008 06:35:30 GMT

Good question. This happened before on my network - it clarifies the pieces of the puzzle.

RE: Waiting on a KILL

Anipaul — Tue, 02 Dec 2008 02:24:15 GMT

Check this:http://www.microsoft.com/technet/prodtechnol/sql/2005/mgsqlexpwssmse.mspx

RE: Waiting on a KILL

Tom Brown — Mon, 01 Dec 2008 10:20:02 GMT

I randomly chose an answer, just to get at the answers to see which was right - but now I'm even more confused. :unsure:

RE: Waiting on a KILL

OCTom — Mon, 01 Dec 2008 09:54:43 GMT

The article referenced is no longer valid. A more up-to-date answer would be appreciated. It seems to me that what was listed as the correct answer and the roll back answer are equalkly valid and neither is the "best" answer.:unsure:

RE: Waiting on a KILL

Chris Harshman — Mon, 01 Dec 2008 07:14:18 GMT

I thought the only thing that prevented a KILL from working was if the session was calling an extended stored procedure, was the same session that issued the KILL, or you tried to kill a system session?

RE: Waiting on a KILL

Bob Lee — Mon, 01 Dec 2008 07:00:37 GMT

Hey Old Hand,The referenced link in the question reference http://support.microsoft.com/kb/171224says that:APPLIES TOMicrosoft SQL Server 6.0 Standard EditionMicrosoft SQL Server 6.5 Standard EditionBut in your article you attribute the question to SQL 2005. When I run the dbcc command on the 2005 server this is what I see:Msg 207, Level 16, State 1, Line 1Invalid column name 'SUID'.This column having migrated to UID in SQL 2005.But even after trying to modify the script for UID to use the DBCC PSS statement I get:Msg 2526, Level 16, State 3, Line 1Incorrect DBCC statement. Check the documentation for the correct DBCC syntax and options.So it would appear that the functionality for the non-supported process is gone.So I think today's question might need a bit of brushing up. Or at least some clarifying if you don't mind.;)

Waiting on a KILL

blank — Sun, 30 Nov 2008 08:23:15 GMT

Comments posted to this topic are about the item [B]Waiting on a KILL[/B]