January 20, 2009 at 11:07 am
A hard drive died, containing some database .LDF files. It is not recoverable so the databases are not usable. I am fortunate in that the databases are not critical and I have full backups, so a simple restore will be fine.
But, if they were critical, what would be the best method to recover ? The .MDF files are on an unaffected drive. Some are simple recovery and some are full.
January 20, 2009 at 12:48 pm
Whether the databases are critical or not, I think restoring backups would be the best way to recover.
Greg
January 20, 2009 at 1:19 pm
homebrew01 (1/20/2009)
But, if they were critical, what would be the best method to recover ?
Restore the backup. The preferred solution to any such form of disaster is to restore the backups, especially if the databases are critical.
The .MDF files are on an unaffected drive. Some are simple recovery and some are full.
Trying to attach and rebuild the log may result in transactionally inconsistent databases. It may result in suspect databases. Rebuilding a log is a last resort when all else has failed and no backups are available.
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
January 20, 2009 at 1:27 pm
That is exactly the reason why we perform full backups, differentials and transaction log backups. The more frequent the transaction log backups - the less data loss.
You could always try to attach the MDF file without the log file - but if the system crashed it probably would not work. If it did work, I would be concerned about what data was actually lost - and, whether or not the data is consistent.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply