Welcome to the third week of the Database Corruption Challenge (DBCC), this is the third in an about weekly competition. Here is how it works; I have created a corrupt database, hopefully more corrupt or more challenging than the previous week. I then solved the corruption myself, in order to prove that it is possible to fix, without data loss. This week it is possible with no 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.
For those who competed last week or the week before, this is an entirely different database. The familiar Revenue table is gone.
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. 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.
Click here for the Database Corruption Challenge Week 3 Details.
Good luck, lets get started…
This week the first winning solution that included the steps to solve the problem, along with a screenshot, showing the details was submitted by Randolph West. This solution was provided 37 minutes after the competition began. Great work Randolph.
Winner #1 – Randolph West (See his solution)
- #2 – Pasquale Ceglie
- #3 – Patrick Flynn
- #4 – Rob Farley
- Herman Atmadja
- Subhro Saha
- Kumar Muppa
- Neil Abrahams
- Nicolette Boddie
- Michael Docherty
- Michel Bruggeman
- David Patterson
- André Kamman
- Lucas Kartawidjaja
- Shashikant Shakya
- Jon Gurgul
- Rui Bastos
- Seann Alexander
- Ivan Rodriguez Camejo
- Prageet Surheley
- Bogdan Sahlean
- Mohan Baba
- Andrew Pruski
- Arthur Baan
- André Abiscula Guimarães
- John Sterrett
- Henrik Bo Hansen
- 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