I had a disk array go nuts recently and it corrupted MSDB and a an application DB. I could repair MSDB, and we had Full and Log backups for the application DB. Whew! We survived.
BUT! I have a question... I’ll do this in an outline so maybe it will be easier to follow:
1.Let's say that you have a application DB that gets fully backed up at 1:00am
2.It has transaction log backups every 15 minutes
3.The DB gets corrupted at, say, 6pm.
4.The corruption results in the loss of all the records in a user table
5.At 6:30pm, the application actually pulls off inserting records into the table
6.Your checkdb does not run until 8:00pm.
Is there a chance that the transaction log backup will be funky because of inserts (etc) into the corrupted table? To be specific, if there are no records in the table because of the corruption, that could result in inserts that would not have normally happened if there were records in the table. So, when you apply the log backup, it would try to insert duplicate records?
I am sure that I am ignorant of something (like something in the nature of log backups), but I have to ask!