April 23, 2014 at 10:50 am
Hi friends
Executing procedure on management studio usually takes 10 minutes, it took over an hour today. I had no luck to see if there were any locks that is causing the slowness because the sql queries to check locks did not work on our client production db.. May be it's some permissions issue that I'm not able to run sql queries on the master database to check the locks.. So I had no go but to kill the session on my management studio. Rollback has been running for about 2.5hrs now.. I checked the rollback status I get 'SPID 121: transaction rollback in progress. Estimated rollback completion: 0%. Estimated time remaining: 0 seconds. So it's clearly not doing any roll back here. Is there a way to kill the process at the OS level? Since it's production we do not want to bounce the service...
Please help.. thanks much
April 23, 2014 at 11:23 am
Restart SQL.
There isn't a process at the OS level to kill (and if you have the idea of killing threads within SQL from the OS, that'll likely crash the SQL service at best)
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
April 23, 2014 at 11:34 am
I see several temp db locks request-mode SCH-M.. Can the locks in temp db affect other databases?
Thanks
April 23, 2014 at 1:40 pm
No.
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
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply