hemanth.damecharla (2/8/2013)
GilaMonster (2/8/2013)
The only thing you can do for a recovering database is wait. If the schedulers are still hung may require another restart, bear in mind that'll undo any recovery work that's already completed.[font="Verdana"]We should be able to see what the scheduler is waiting on if we query dm_exec_requests based on scheduler id right? Also, since the worker address is mentioned would it be possible to query workers and threads to see what the os thread_id is and then from a performance monitor(assuming OS is win2008) can we see what the problem with the particular thread is?[/font]
Maybe with a debugger and the public symbols, but then what? The schedulers are hung, so you can't kill a session even if you can figure out which one is on the schedulers and it's a user session (which since things are in recovery is unlikely)
If it's a shrink that's getting rolled back/forward, the schedulers are probably stuck in some preemptive section of IO code
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