Killed/Rollback

Question

Killed/Rollback

Shas3

Hall of Fame

Points: 3671
More actions
October 4, 2004 at 9:21 am

#163426

Is there any way I can get rid of the Killed/Rollback processes from the sysprocesses with out restarting the sql server service??? These transaction are struck from 3 to 4 days has nothing but an active connection to sql server and no active connection on OS side however it showing the KPID a non zero value.

Thanks
shas3

Shas3

Viewing 13 posts - 1 through 12 (of 12 total)

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

sa24 SSCrazy Eights Points: 8027 More actions · Answer 1

A non zero kpid means that the spid is in runnable state. Try to recylce the service or program which created this spid.

Steve Jones - SSC Editor SSC Guru Points: 737159 More actions · Answer 2

If KILL won't do it, and I'd be sure to run it a few times, you have to restart the server.

Shas3 Hall of Fame Points: 3671 More actions · Answer 3

Nope. I sure don't want to restart the service.

Shas3

iLoveSQL SSCrazy Points: 2888 More actions · Answer 4

I have a same situation (one Kill/Rollback process has been hanging last six month) and I just didn't want to restart the service just because of that. It just bug me but I don't see any bad side of it until next time I HAVE TO restart the service for other compaling reason..

Shas3 Hall of Fame Points: 3671 More actions · Answer 5

Just spoke with the MS rep and the only way that we can clear those SPIDS is to cycle the service after the process has been killed

Shas3

Steve Jones - SSC Editor SSC Guru Points: 737159 More actions · Answer 6

I thnk you are probably ok with leaving it until you can reboot. I've had DTS jobs that I've killed from DTS as well as SQL and just let them run,

SQLArch Ten Centuries Points: 1322 More actions · Answer 7

SQLArch

Ten Centuries

Points: 1322

October 5, 2004 at 9:05 am

#525429

Having same issues.

How to cycle the service?

John J Fell Newbie Points: 3 More actions · Answer 8

I am currently having the same problem, I have 3 processes like that. Can this prevent replication of a database. I believe that is preventing my replication from working, I have 2 other databases being replicated the exact same way, it is only the one which has locked processes and is failing. How do you recyle the service? and which service are you talking about?

iLoveSQL SSCrazy Points: 2888 More actions · Answer 9

Unfortunatly, it is SQL Services. If you have an instance, you can just restart the instance of that but still, it is still SQL Service. (i.e MSSQLSERVER for default instance).

Just to make sure to restart the sql agent manually if you are only going to restart the service only not rebooting the box. I've seen many folks leave the agents to be not started for a while until they realized that the backup/maintenance jobs weren't working

Sandip-31Oct SSC-Addicted Points: 494 More actions · Answer 10

I had the same issue. I wait two days and waiting to clear the killed/rollback process by itself. I am end up with restart the SQL service and it clears.

Sandip

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 11

Please note: 6 year old thread.

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

Alvin Ramard SSC-Forever Points: 41190 More actions · Answer 12

GilaMonster (8/31/2010)
Please note: 6 year old thread.

I wonder if someone forgot to do a RESET after running DBCC TimeWarp 😀

Alvin Ramard
Memphis PASS Chapter[/url]

All my SSC forum answers come with a money back guarantee. If you didn't like the answer then I'll gladly refund what you paid for it.

For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]