Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Stop Recovery Progress. Urgent help needed Expand / Collapse
Author
Message
Posted Wednesday, March 26, 2008 8:33 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Monday, November 25, 2013 8:08 AM
Points: 490, Visits: 1,383
One of my database is in recovery process. I need to stop it. I don't care if I lose data in log file. I want to delete log file but cannot.
Is there a way to stop recovery process.



Post #475183
Posted Wednesday, March 26, 2008 8:55 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Yesterday @ 11:23 PM
Points: 33,278, Visits: 15,449
Pull the plug! Not sure that you can do anything else.

There is a switch to start SQL Server without going through recovery.

Why do you want to stop it? This is recovery, on the restart of the instance and not restore, correct?







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #475187
Posted Wednesday, March 26, 2008 9:05 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Monday, November 25, 2013 8:08 AM
Points: 490, Visits: 1,383
Is it recovering uncommitted transaction from the transaction log file. If that is the case then I can open database with out transaction log file and let system will create a new log file.
My log file is growing and no space on the drive.

I don't know what recovery process is doing and how long it takes.



Post #475195
Posted Wednesday, March 26, 2008 11:10 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Wednesday, September 17, 2014 6:29 PM
Points: 344, Visits: 290
I think I am late in party :)
I would never recommend to stop recovery process. No one can stop you doing suicide but thats crime

Jokes apart, You could stop SQL Server in such cases, rename the transaciton log. This will bring database into suspect mode. Then you can run some command to rebuild the log after brining database in to Emergency mode. SQL 2005 has ALTER DATABASE SET EMERGENCY command.


Let me know if you want more details - bmlakhani@yahoo.com

Post #475222
Posted Thursday, March 27, 2008 2:23 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, February 27, 2014 3:44 AM
Points: 179, Visits: 331
As of now there is no proper way to quit from an ongoing restore....if anyway you interrupt the restore process, the state of the database will be set to 1 and the database property 'IsShutDown' for the database is set to null....and there is no way of updating the system tables with adhoc queries......so its upto the MS SQL Server Development team to provide the feature of restore rollback in the next version......

Chandrachurh Ghosh
DBA – MS SQL Server
Ericsson India Global Services Limited
Quality is not an act, it is a habit.
Post #475262
Posted Thursday, March 27, 2008 2:45 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, April 15, 2014 10:36 AM
Points: 1,199, Visits: 574
you can use trace 3607; it should skip the recovery process. Hope you have the backups in place:)
Post #475272
Posted Thursday, March 27, 2008 5:23 PM


Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 10:19 AM
Points: 3,089, Visits: 1,435
Did you solve your problem?




My blog
Post #475831
Posted Friday, March 28, 2008 7:09 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Friday, January 6, 2012 2:39 PM
Points: 954, Visits: 683
I suspect that a recovery was started and left so that more logs could be applied.
RESTORE DATABASE [analysis] WITH NORECOVERY

I would suggest trying to recover to read only mode first.
RESTORE DATABASE [analysis] WITH STANDBY = 'D:\Program Files\Microsoft SQL Server\SQL2005\MSSQL.1\MSSQL\Backup\ROLLBACK_UNDO_analysis.BAK'

Or just try and fully recovery
RESTORE DATABASE [analysis] WITH RECOVERY

Post #476066
Posted Friday, May 9, 2008 9:45 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Yesterday @ 7:57 AM
Points: 986, Visits: 1,327
"Then you can run some command to rebuild the log ...." and that is? I'm having the same issue and I was able to rename the log but was not sure how to rebuild the log.

Your help is greatly appreciated

Kurt
.


Kurt W. Zimmerman
SR DBA
Lefrak Organization
New York, NY

http://www.linkedin.com/in/kurtwzimmerman
Post #498023
Posted Friday, May 9, 2008 11:37 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Monday, November 25, 2013 8:08 AM
Points: 490, Visits: 1,383
Thanks for all your help.
The recovery process ran for some time and then recovered the database. I did not do anything but to wait.



Post #498119
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse