Neil Abrahams Interview – Database Corruption Challenge

Download PDF

After 10 weeks (or almost weekly) of corrupt databases, missing data and a challenging competition the Database Corruption Challenge finally comes to an end. As part of the last week of the challenge I created a short blog interview for the participants. This interview is Neil Abrahams.NeilAbrahams

Neil placed in third place with a 3 way tie for third overall in the the Database Corruption Challenge scoring 21 points. He was one of only 3 participants to complete all 10 challenges in the contest, the other two were André Kamman and Rob Farley.

Here are the overall statistics for Neil in the Database Corruption Challenge

Neil Abrahams Interview

What compelled you to want to participate in the Database Corruption Challenge?

Neil: I had spent a lot of time learning DB internals, Corruption over the last few years. Corruption is regarded as highly advanced topic and I wanted to know how much or little I knew and how I could deal with it on a practical level.

What did you find the most interesting in the Database Corruption Challenge?

Neil: The number of ways you could recover the DB.

What did you learn in the Database Corruption Challenge?

Neil: I’ve learned to widen my view point of how to recover the data. The Change Data Capture week was a light bulb moment. It was the illusive obvious.

How many weeks did you participate in the Database Corruption Challenge?

Neil: 10 Weeks

Any suggestions to those who might want to give some of the 10 Database Corruption Challenge examples a try?

Neil: As a free resource all database processionals in charge of recovery should walk through each week and ensure they know the way to get the data back.


Neil has also written his first blog post discussing the database corruption challenge on on Linked In.

Related Links

Database Corruption Challenge Sponsored by Stedman Solutions, LLC.

Tagged with: , ,

Leave a Reply

Your email address will not be published. Required fields are marked *


Time limit is exhausted. Please reload CAPTCHA.