September 11, 2012 at 4:18 am
Hi all,
I was creating a partition using the partition wizard and the transaction log began to get bigger and bigger until it reaches the maximun disk capacity.
Then I canceled the operation and the wizard stuck.
I restarted the service and when I opened the SSMS again my database is marked as "In Recovery".
What can I do to fix this issue?
Any comment would be appreciated.
Kind Regards,
Paul
September 11, 2012 at 4:24 am
Wait.
Recovery takes time. When you restarted SQL, the transaction hadn't finished rolling back, so now it has to finish rolling back before the DB can be brought online.
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
September 11, 2012 at 5:36 am
Thanks so much GilaMonster:
I´m still waiting but now I´m able to calm down 🙂
I found this blog entry which shows how to determine aprox. how low does the database will be in recovery mode:
http://timlaqua.com/2009/09/determining-how-long-a-database-will-be-in-recovery-sql-server-2008/
Kind Regards,
September 11, 2012 at 5:49 am
The estimation in the error log can be on the low side. Expect at least as long as the operation took before you stopped it and restarted SQL.
btw, you didn't need to restart. The partitioning would have rolled back with the DB online and just the table involved in the partitioning would have been unavailable (locked)
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