Welcome to the sixth week of 10 in the Database Corruption Challenge (DBCC), this is an about weekly competition. Here is how it works; I have created a corrupt database, hopefully more corrupt or more interesting than the previous week. I then solved the corruption myself, this time I solved it 2 different ways in order to prove that it is possible to fix, without data loss.
I then post the challenge including the database download and announce it. Those who subscribe to my newsletter will get advance notice to know when it is going to be posted.
The challenge will be to download the corrupt 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.
Points will be scored as follows:
- 2 points to the first person to provide a correct solution.
- 1 point for all other correct solutions (you can only get this once, providing 2 correct solutions does not earn you 2 points).
- 1 point for linking to http://SteveStedman.com/corruption (you can only earn this once in the 10 weeks).
- There is a bonus point available this week for adding a comment to the DBCC CheckDB speed blog post. All who answer the question of what you do when CheckDB is slow and post it as a response to the blog, will earn a bonus point.
This week the first winning solution that included requirements above was from Raul Gonzalez. Great work Raul !!! The solution was submitted just 45 minutes after tehe challenge began.
#1 Raul Gonzalez
- #2 Andrei Stefan
- #3 Patrick Flynn
- Randolph West
- Herman Atmadja
- Michael Docherty
- Neil Abrahams
- Jon Gurgul
- Lucas Kartawidjaja
- Subhro Saha
- Rob Farley
- Ivan Rodriguez Camejo
- Kumar Muppa
- André Kamman
- Pasquale Ceglie
- Arthur Baan
- David Patterson
- Bogdan Sahlean
- Current Scores
- Newsletter Sign up
- Database Corruption Challenge T-Shirt
- Week 1, Week 2, Week 3, Week 4, Week 5, Week 6, Week 7, Week 8, Week 9, Week 10
- Slow DBCC CheckDB
- Database Corruption Worksheet