Lately several people have asked me for the solutions to the corruption challenge, so I thought it would be a good time to recap the last 7 weeks. Week 1 of the Database Corruption Challenge was won by Brent Ozar, his solution is posted here. Also there is an alternate solution provided by Andre Kamman. Week 2 of the Database Corruption …
Today I am presenting to the session “When Database Corruption Strikes” to the High Availability and Disaster Recovery PASS Virtual Chapter. Here is the abstract: You are working along month after month with no problems in your database. Suddenly someone reports that their query won’t run. They get an error stating “SQL Server detected a logical consistency-based I/O error“, or …
The alternate solution to the Database Corruption Challenge this week was created by Patrick Flynn. This solution is the only solution to successfully recover all the data without using any of the backups. If the challenge had been structured differently and all you had was just the database files and no backups, this solution would work just fine. As you …
Database Corruption Challenge Week 7 – Alternate Solution Read more »
How do you check if a database exists, drop it and recreate it for testing purposes? After running the Database Corruption Challenge for several weeks now, I have seen many scripts to drop and recreate a database. This makes it clear that it takes many tries to get the corruption challenge right. They usually start out with something like the …
The seventh week of ten in the Database Corruption Challenge went well. There were a few new participants, and many of those who have competed week over week. The first to submit a correct answer this week was Raul Gonzalez. What was interesting about this challenge was that it was not your typical corruption where you could just run DBCC CheckDB and …
Welcome to the seventh 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 in order to prove that it is possible to fix, without data loss. New …
Those who are subscribed to my newsletter will receive the exact time of the next corruption challenge. For those who have not subscribed, just keep checking back to find out when the next Database Corruption Challenge begins. Here is the latest update on how the challenge has gone so far: Week 1 was just a wild idea that I had to …
If you are looking for more info on the corrupt database with Week 6 of the Database Corruption Challenge, you can take a look at the original post. Week 6 was won by Raul Gonzalez who submitted his winning solution just 45 minutes after the challenge began. Raul has solved 4 of the 6 challenges so far, and has scored …
Week 6 – The Winning Solution – Database Corruption Challenge Read more »
Welcome to the Week 6 Corruption Challenge. If you have seen the t-shirt that I designed for the winner at the end of the 10 week period, please take a look. For this challenge, any version of SQL Server 2005 or newer will work, however I don’t know on Azure.
There are many times that CheckDB ends up being extremely slow, sometimes taking more than a day to run. This can make life difficult if you are trying to find out what is corrupt. There are several of the tricks that I use to speed up DBCC CheckDB, depending on the specific environment. What I am looking for is what others do …