Process still runnable

Question

Post reply

Process still runnable

Maverick100877

SSCertifiable

Points: 5240
More actions
September 19, 2006 at 6:35 am

#170277

Hi
There is a vb program which runs. Now this has started taking a lot of time. So the users abandon the process in between( they cancel the vb program). But when I see in sql the process is still runnable.
Well then I kill the process but even after that it stays there with the runnable status.
It either shows this messages
SPID 55: transaction rollback in progress. Estimated rollback completion: 100%. Estimated time remaining: 0 seconds.
or
SPID 54: transaction rollback in progress. Estimated rollback completion: 0%. Estimated time remaining: 0 seconds.
Why are these processes still showing there??

Viewing 7 posts - 1 through 6 (of 6 total)

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

Jo Pattyn SSC-Dedicated Points: 32348 More actions · Answer 1

The process needs to be kept alive till the rollback is completed (which can also take a long time).

Any clues why the vb app suddenly started to work slower?

Maverick100877 SSCertifiable Points: 5240 More actions · Answer 2

Well I'm trying to figure that out. It is getting stuck at a particular updated statement. But why is the process still running when I have killed and rollback completed 100%.

Jo Pattyn SSC-Dedicated Points: 32348 More actions · Answer 3

It should die soon after that. Do you check it with sp_who?

Maverick100877 SSCertifiable Points: 5240 More actions · Answer 4

No it is not.It was there for almost 2 days with the runnable status. I use sp_who2 active.

Jeff Gray SSChampion Points: 10667 More actions · Answer 5

I've had that sort of thing happen when I call an application from SQL server, and then terminate the application "forcibly". The SPID will not finish rollback because the nonexistent instance of the dead application will never return an exit code to SQL. So it sits until the SQL service is restarted.

This has also happened when killing a SPID that has called a normal sproc on a linked server. If it isn't blocking anything, it shouldn't be a problem. It will have to wait until you can restart SQL.

hth jg

Maverick100877 SSCertifiable Points: 5240 More actions · Answer 6

Hi

the problem is that it is doing an update and is blocking other statements from getting executed. So I have no other option but to the start the sql server services again.

But why is it so that even after killing it the process is blocking other processes.