Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Waiting on a KILL


Waiting on a KILL

Author
Message
blank
blank
Old Hand
Old Hand (371 reputation)Old Hand (371 reputation)Old Hand (371 reputation)Old Hand (371 reputation)Old Hand (371 reputation)Old Hand (371 reputation)Old Hand (371 reputation)Old Hand (371 reputation)

Group: General Forum Members
Points: 371 Visits: 77
Comments posted to this topic are about the item Waiting on a KILL
Bob Lee
Bob Lee
SSC-Enthusiastic
SSC-Enthusiastic (131 reputation)SSC-Enthusiastic (131 reputation)SSC-Enthusiastic (131 reputation)SSC-Enthusiastic (131 reputation)SSC-Enthusiastic (131 reputation)SSC-Enthusiastic (131 reputation)SSC-Enthusiastic (131 reputation)SSC-Enthusiastic (131 reputation)

Group: General Forum Members
Points: 131 Visits: 356
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.

Wink
Chris Harshman
Chris Harshman
Hall of Fame
Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)

Group: General Forum Members
Points: 3285 Visits: 3540
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
OCTom
SSCrazy
SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)SSCrazy (2.9K reputation)

Group: General Forum Members
Points: 2869 Visits: 4152
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
Tom Brown
Tom  Brown
UDP Broadcaster
UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)

Group: General Forum Members
Points: 1469 Visits: 1468
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
Anipaul
SSCertifiable
SSCertifiable (6.6K reputation)SSCertifiable (6.6K reputation)SSCertifiable (6.6K reputation)SSCertifiable (6.6K reputation)SSCertifiable (6.6K reputation)SSCertifiable (6.6K reputation)SSCertifiable (6.6K reputation)SSCertifiable (6.6K reputation)

Group: General Forum Members
Points: 6567 Visits: 1407
Check this:

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



Jamie-2229
Jamie-2229
Hall of Fame
Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)Hall of Fame (3K reputation)

Group: General Forum Members
Points: 3033 Visits: 832
Good question. This happened before on my network - it clarifies the pieces of the puzzle.

Jamie
TomThomson
TomThomson
SSChampion
SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)

Group: General Forum Members
Points: 11589 Visits: 12105
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
TomThomson
SSChampion
SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)SSChampion (11K reputation)

Group: General Forum Members
Points: 11589 Visits: 12105
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

Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search