Restore Database Without Log

Question

Restore Database Without Log

Viewing 5 posts - 16 through 19 (of 19 total)

You must be logged in to reply to this topic. Login to reply

Paul Randal One Orange Chip Points: 29544 More actions · Answer 1

Paresh Prajapati (1/16/2009)
Tim Riley (1/8/2009)
I know there is, but I can't remember how...How do you go about restoring a database that has a corrupt/bad transaction log?
Please take a tail log og current db, then restote full backup with no recovery and then restore log with recovery, if u got error then apply option continue_after_error...

And how would that work if the transaction log is corrupt? (As the entire rest of the thread that you skipped was discussing...)

Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005

Paresh Prajapati SSCertifiable Points: 7567 More actions · Answer 2

Paul Randal (1/17/2009)
Paresh Prajapati (1/16/2009)
Tim Riley (1/8/2009)
I know there is, but I can't remember how...How do you go about restoring a database that has a corrupt/bad transaction log?
Please take a tail log og current db, then restote full backup with no recovery and then restore log with recovery, if u got error then apply option continue_after_error...
And how would that work if the transaction log is corrupt? (As the entire rest of the thread that you skipped was discussing...)

That'y i said to take transaction log backup of current DB again and then apply it after that..

_____________________________________________________________________________________________________________
Paresh Prajapati
➡ +919924626601
http://paresh-sqldba.blogspot.com/[/url]
LinkedIn | Tweet Me | FaceBook | Brijj

Lynn Pettis SSC Guru Points: 442467 More actions · Answer 3

Paresh Prajapati (1/17/2009)
Paul Randal (1/17/2009)
Paresh Prajapati (1/16/2009)
Tim Riley (1/8/2009)
I know there is, but I can't remember how...How do you go about restoring a database that has a corrupt/bad transaction log?
Please take a tail log og current db, then restote full backup with no recovery and then restore log with recovery, if u got error then apply option continue_after_error...
And how would that work if the transaction log is corrupt? (As the entire rest of the thread that you skipped was discussing...)
That'y i said to take transaction log backup of current DB again and then apply it after that..

If you had read the entire thread you would also note that the database was using the simply recovery model. That means you couldn't take a tail-log backup.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 4

Paresh Prajapati (1/17/2009)
That'y i said to take transaction log backup of current DB again and then apply it after that..

Except that, as Paul said, if the log's corrupt when you restore a full and you have to use continue after error, you CANNOT apply any further backups. Not diff (which the OP had) and not log.

Oh, and since the diff wouldn't restore due to the damaged log, even if it were possible to take a tail-log backup, it wouldn't be possible to restore it because the LSNs wouldn't match. The log backup would be based off of the diff (assuming no log backups had been taken since the diff), which didn't restore.

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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Paul Randal One Orange Chip Points: 29544 More actions · Answer 5

Paresh Prajapati (1/17/2009)
Paul Randal (1/17/2009)
Paresh Prajapati (1/16/2009)
Tim Riley (1/8/2009)
I know there is, but I can't remember how...How do you go about restoring a database that has a corrupt/bad transaction log?
Please take a tail log og current db, then restote full backup with no recovery and then restore log with recovery, if u got error then apply option continue_after_error...
And how would that work if the transaction log is corrupt? (As the entire rest of the thread that you skipped was discussing...)
That'y i said to take transaction log backup of current DB again and then apply it after that..

That can't ever work - you'd be missing all the log between the full backup and the most recent log backup. Go read the article on Understanding Logging and Recovery I wrote for this month's TechNet Magazine (http://technet.microsoft.com/en-us/magazine/2009.02.logging.aspx).

Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005