Last week we had some databases with a corrupt transaction log files. This happenend while our SAN operators were moving de databases to a new SAN (which didn't go well this time, although we took SQL Server offline first).
I have resolved the problems with the help of the article below (thanks Gail):http://www.sqlservercentral.com/Forums/Topic733084-266-1.aspx
I detected the corrupt logfiles, because the log backups where failing with the error "Backup detected log corruption in database".
DBCC CHECKDB didn't warn me.
How can I check if my transaction logs are OK, because for databases that are using the Simple recovery model, you don't run a log backup.
This week I failed the instance to another node and I discovered that the log of the master database was corrupt. So I had to rebuild and restore the master to get my SQL server up and running again. Master is using the simple recovery model, so how could I have known it's log was corrupted?