Database Corruption Challenge

In 2015, around the time I started Stedman Solutions LLC, I created the Database Corruption Challenge as a way to share knowledge of how to repair corrupt databases and to provide options to running REPAIR_ALLOW_DATA_LOSS.

Today the lessons from the corruption challenge are just as valid as they were in 2015, it is a good place to start if you are looking for ways to fix your own corrupt database.

If you have checkDB errors, or you are getting SQL Server error 823 or 824, or your database is in suspect mode, take a look at the database corruption challenge, or get in contact with Stedman Solutions, LLC.

Database Corruption Challenge History

• Week 1 Database Corruption Challenge 4/11/2015 won by Brent Ozar. (See the solution)
• Week 2 Database Corruption Challenge 4/17/2015 won by Rob Farley. (See the solution)
• Week 3 Database Corruption Challenge 4/24/2015 won by Randolph West. (See the solution)
• Week 4 Database Corruption Challenge 5/1/2015 won by Randolph West. (See the solution)
• Week 5 Database Corruption Challenge 5/12/2015 won by Patrick Flynn. (See the solution)
• Week 6 Database Corruption Challenge 5/23/2015 won by Raul Gonzalez. (See the solution)
• Week 7 Database Corruption Challenge 6/2/2015 – won by Raul Gonzalez. (See the solution)
• Week 8 Database Corruption Challenge 6/19/2015 – won  by Rob Farley. (See the solution)
• Week 9 Database Corruption Challenge 7/6/2015 – won by  Eduardo Rezende. (See the solution)
• Week 10 Database Corruption Challenge 7/17/2015 – won by Rob Farley. (See the solution)

The Corruption Challenge started in April of 2015 and ran through July of 2015. Many participated, many solved corruption, and many people learned something along the way.

And as always if you need help with repairing a corrupt database, we can help.

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!