Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Waiting on a KILL Expand / Collapse
Author
Message
Posted Sunday, November 30, 2008 8:23 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, December 1, 2008 8:01 AM
Points: 369, Visits: 77
Comments posted to this topic are about the item Waiting on a KILL
Post #610879
Posted Monday, December 1, 2008 7:00 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Thursday, May 24, 2012 2:06 PM
Points: 97, 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.

;)
Post #611295
Posted Monday, December 1, 2008 7:14 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Yesterday @ 3:19 PM
Points: 1,913, Visits: 2,062
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?
Post #611315
Posted Monday, December 1, 2008 9:54 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 9:29 AM
Points: 2,610, Visits: 3,968
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.



Post #611465
Posted Monday, December 1, 2008 10:20 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, October 22, 2014 7:48 AM
Points: 1,221, Visits: 1,433

I randomly chose an answer, just to get at the answers to see which was right - but now I'm even more confused.
Post #611483
Posted Tuesday, December 2, 2008 2:24 AM
SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Thursday, October 16, 2014 4:46 AM
Points: 5,415, Visits: 1,400
Check this:

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




Post #611890
Posted Tuesday, December 2, 2008 6:35 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Tuesday, September 23, 2014 2:10 PM
Points: 2,669, Visits: 781
Good question. This happened before on my network - it clarifies the pieces of the puzzle.

Jamie
Post #612011
Posted Tuesday, December 7, 2010 10:44 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 7:54 AM
Points: 7,814, Visits: 9,562
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
Post #1031396
Posted Tuesday, December 7, 2010 10:47 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 7:54 AM
Points: 7,814, Visits: 9,562
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.



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
Post #1031398
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse