Importance of Backups Relating to a Corrupt Database

At Stedman Solutions, LLC when we do corruption repair it usually means someone has discovered they have corruption, and they call us. If they had good backups and good CheckDB scripts, they wouldn’t have to call us because they would have known when the corruption happened and likely been able to restore from backup or restore and replay transaction logs to get past the corruption.

Corruption repair is the highest billing service that we charge for, and it can be extremely expensive for us to rebuild or repair a corrupt database.

Recently one of our clients had a corrupt database, and they were using our recommended backup strategy with regular full backups, more frequent differential backups and transaction log backups. That corruption repair turned into a short phone call with instructions on how to start restoring backups, then a second follow up phone call when they were almost done, overall it was about 2 hours of billable time at our standard rate, rather than days of time at our highest rates. They were able to do the restore with a couple hours of downtime and then replay the transaction logs past where the corruption was introduced to get back to a good state with no corruption.

The point I am trying to make is that having good backups can make all the difference in the world if you end up with a corrupt database. You have far more options.

​SQL Server Backup and Recovery Class

This complete course will help you determine if you have a sufficient backup strategy and restore plan OR will help you build one from scratch.

More from Stedman Solutions:

Steve and the team at Stedman Solutions are here for all your SQL Server needs.
Contact us today for your free 30 minute consultation..
We are ready to help!