January 18, 2008 at 4:52 am
I was updated a few records(245) then I rollback it.
it goes in hung state.
So I use kill after 15 minutes.
But still after 30 mins it shows me runnable & values of CPU & DiskIO in
sp_who2 active shows as it is as it was previous.
Can u tell How do delete this process. after only deleting this process I can
use updation on it..
plz suggest..
January 18, 2008 at 7:49 am
Hi,
Is the process showing up as in a KILLED/ROLLBACK state?
First thing you want to do is check the status of the process you killed by running KILL {spid | UOW} WITH STATUSONLY which will show you where you are in the rollback process. If it tells you that the process is 100% complete with 0ms remaining the process has been killed and rolledback but sql is keeping it around and the only way to remove the entry is to restart the server (not a very popular option).
Hope this helps!
Jeff 😎
January 18, 2008 at 8:02 am
Hi Jeff,
I have already killed that process, but still it shows entry in sp_who2 active
as
128
RUNNABLE--walkers-- SOFT41--PRINT_2008--KILLED/ROLLBACK
And also when I check it's status in Kill .It shows as u stated above.
Wht I have to do..
I have to restart services only or server.
because I try to restart services but nothing effective.
It goes in hung state. Not working.
What should I do.. Plz reply..
January 18, 2008 at 8:07 am
If its possible in your situation, restart the server and everything should clear up. I've run into instances where restarting the SQL Server Service has cleared things up and other time where I've had to reboot the server. I looks like stopping/starting the SQL Server service didn't do it for you. So, the only option you have left is to reboot.
~Jeff
January 18, 2008 at 8:46 am
It's working now..
After restarting/rebooting server, it get flush out & not showing.
Thanks a lot Jeff.
Regards
Majid
January 18, 2008 at 8:49 am
np 😎
January 18, 2008 at 8:52 am
If you run the same process, does it hang again? If so, I might report this to Microsoft.
I've seen this happen before and had it reported here a lot. It would be good to give MS knowledge on what you were doing so they can look into it. Maybe report it as a Connect bug if you can reproduce it.
January 19, 2008 at 2:09 am
Yes jeff.
U are right.
I use the same query & again I face same the problem.
Acually I m updating few(245 records) records on 'X' database which is on one server from 'Y' database which is on other server using linked server.
When I try to execute this query it first gives me error
MSDTC is not available on 'servername'
Then I restarted a service 'Distributed transaction coordinator'.
After that I executed same query & it goes in hung state.
Where I can report for this & how.
can u suggest me...
I have to resolve this issue.
Regards
Majid
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply