Database Corruption Challenge #10

Welcome to Week 10 of the Database Corruption Challenge. I have created a more corrupt, and perhaps more diabolical corruption scenario than previous weeks. This is the last week of 10 in the Database Corruption Challenge.

Here is how it works; I have created a corrupt database, then solved the corruption myself in order to prove that it is possible to fix, without data loss.

Database Corruption Challenge Details

There will be a total of 6 points available in this weeks challenge.

1 point for being the first to solve the corruption challenge, and posting something about the corruption challenge on Twitter or LinkedIn. Please reference http://SteveStedman.com/Corruption in the post.
1 point for having the solution right the first time you submit your solution.
3 points for solving all the corruption with no data loss and providing the TSQL code (or other detailed steps) that was used to fix the corruption.
1 point for completing the Blog Interview Questions. This does not have to be submitted with your solution, but it does need to be submitted by the end of the competition.

Extra Clue

There will be no extra clue this week. This is the final challenge, and it must be solved without any extra clues.

Corruption Challenge General Info

The challenge will be to download the corrupt or somehow damaged database and attempt to recover it. If you can recover it, please send me the steps you used to recover the database, along with some proof that the database has been recovered. The goal each week will be the following:

Recover the database to your best ability.
You need to be able to bring the database online and run queries against it.
For any corruption that causes data loss, you need to figure out how to restore as much of the missing data with what you have been given.

When you come up with your solution, send me your result by email. Tell me what you did to fix the corruption, what you did to restore data (if that as needed), and include proof. The proof could be a screen shot, showing the solution, it could be a TSQL Script with the solution, or something else. I will validate and confirm if your result is correct. Depending on the number of people who send me results, this may take a while.

The first person who sends me a correct result will get their name posted on my blog as the winner of this weeks DataBase Corruption Challenge (DBCC). Others who send me a correct solution by the deadline will also get their name posted. Some of the first, accurate and unique solutions will be posted on the resulting blog post. If you don’t wish to have your name associated with your results, please ask to remain anonymous, and I will not use your name. Unless you specify otherwise, anything you send me may be used on the blog to tell the story of how to solve the corruption.

Challenge #10

See the Challenge 10 Detail page for info on this challenge.

Whats next?

After this challenge is complete, and the winners are posted, I will be sending out a short survey looking for feedback on some ideas that I have for where to go once this challenge is complete. If you can take the time to answer these questions when the survey comes out it would be greatly appreciated.