January 22, 2014 at 1:36 pm
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?
Regards,
Marco
January 27, 2014 at 11:59 am
Actually, I just had the same thing happen to me over the weekend, and I had the same question: short of BACKUP LOG, is there some way that I can check the integrity of the Transaction Log file(s) for my databases?
Thx.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply