Friday, March 9, 2012

Recover Bad Logs

SQL Server 2000
We have a database that crashed and the log file is bad and the last good
backup was october, so the transaction log is bigger than the data file.
Since the transaction log is corrupt,and we have no backups because the last
good backup was october, can I do something with that corrupt transaction log
to get those transactions out of it and bring forward the database to be
current with all transactions?
Need some help. This is a production DB.
Chris Davoli
"Chris Davoli" <ChrisDavoli@.discussions.microsoft.com> wrote in message
news:044D39A3-23A9-424A-93AC-A8D063962B5C@.microsoft.com...
> SQL Server 2000
> We have a database that crashed and the log file is bad and the last good
> backup was october, so the transaction log is bigger than the data file.
> Since the transaction log is corrupt,and we have no backups because the
> last
> good backup was october, can I do something with that corrupt transaction
> log
> to get those transactions out of it and bring forward the database to be
> current with all transactions?
Call Microsoft. Most likely your DB is hosed. But sometimes they can work
miracles.

> Need some help. This is a production DB.
> --
> Chris Davoli
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html

No comments:

Post a Comment