Waiting on a KILL

Question

Post reply

Waiting on a KILL

blank

SSC-Addicted

Points: 479
More actions
November 30, 2008 at 8:23 am

#194511

Comments posted to this topic are about the item Waiting on a KILL

Viewing 9 posts - 1 through 8 (of 8 total)

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

Bob Lee SSC Eights! Points: 871 More actions · Answer 1

Hey Old Hand,

The referenced link in the question reference http://support.microsoft.com/kb/171224

says that:

APPLIES TO

Microsoft SQL Server 6.0 Standard Edition

Microsoft SQL Server 6.5 Standard Edition

But 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 1

Invalid 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 1

Incorrect 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.

😉

Chris Harshman SSC-Forever Points: 42192 More actions · Answer 2

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?

OCTom SSChampion Points: 11785 More actions · Answer 3

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:

Tom257 SSChampion Points: 11543 More actions · Answer 4

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

Anipaul SSC-Insane Points: 24681 More actions · Answer 5

Check this:

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

Jamie-2229 SSCrazy Eights Points: 8156 More actions · Answer 6

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

Jamie

TomThomson SSC Guru Points: 104773 More actions · Answer 7

Chris Harshman (12/1/2008)
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?

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.

Tom

TomThomson SSC Guru Points: 104773 More actions · Answer 8

OCTom (12/1/2008)
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:

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.

Tom