February 5, 2013 at 7:30 am
Hi All
After doing some Research & Testing on corruption, I have a question.
>> Database is corrupt
>> Determined that it's the transaction log that is corrupt. Confirmed this by checking the error log and found "SQL Server detected a logical consistency-based I/O error: incorrect checksum............................ldf"
I am well aware that detaching a corrupt database is not a good thing.
If I know that SQL was shutdown cleanly - Is it then semi-ok to detach the database and then re-attach with attach_rebuild_log ?
Thoughts?
February 5, 2013 at 8:45 am
It's of course risky... but if only the log is corrupted then detaching the db then do a attach single file db *should* work. I'm not saying that you should do this or that it definitely will work....but it should 🙂
be careful!
February 5, 2013 at 8:52 am
How would you get an incorrect checksum in the log anyway?
Checksums are on database pages in the data file.
There are instances of log corruption, that's not one of them.
Absolutely do not detach and delete the log. Unless you want to convert corrupt and online database into database that won't attach.
Take a look at this article. http://www.sqlservercentral.com/articles/65804/ and see the list of Do Nots.
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 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply