Speaking at PASS Summit 2016
This year in October, I again have the privilege to speak at PASS Summit in Seattle. One of my favorite topics, Database Corruption was the… Read More »Speaking at PASS Summit 2016
This year in October, I again have the privilege to speak at PASS Summit in Seattle. One of my favorite topics, Database Corruption was the… Read More »Speaking at PASS Summit 2016
Please join Carlos and I for our first Database Corruption webcast on May 3rd. I have teamed up with Carlos and we will be presenting some thoughts on database corruption with an extended Q&A session.
One important detail is we will be taking questions and answering them live on the webcast so this will be a great way to engage and ask a follow up if needed. I think you will love this format–way better than soaking up 50 minutes of boring and then calling it quits.
The webcast will cover these major topics.
1) Preparing for database corruption and taking the right steps to ensure you can recover
2) A few lessons learned about our experience with database corruption
This weeks session will cover:
The best DR plan still needs to account for corruption.
This Saturday, September 12th, 2015 I will be presenting at SQL Saturday Las Vegas. My presentation is on Database Corruption, here are the details.
Duration: 60 minutes
Track: Enterprise Database Administration & Deployment
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 something even scarier. Do you know what to do now? We will walk through 3 or 4 actual corrupt databases exploring ways to go about finding and fixing the corruption. More importantly we will explore how to prevent further data loss at the time corruption occurs. Learn what things you should do to protect yourself when corruption strikes. Learn what to avoid that will make things worse. You will leave with a checklist of steps to take when you encounter corruption. By the end of this session you will be ready to take on corruption, one database at a time.
The presentation is scheduled for 11:00 am to Noon in room 2767 at the College of Southern Nevada campus in Vegas.
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.
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
Read More »Neil Abrahams Interview – Database Corruption Challenge
Hello everyone, the last week I have not been able to keep everyone as up to date on the Database Corruption Challenge as I would… Read More »Database Corruption Challange 6 – Coming Soon
Here is how I solved Week 5 of the Database Corruption Challenge. The following steps were tested and confirmed working on SQL Server 2008R2, SQL Server 2012, and SQL Server 2014.
To oversimplify, here are the steps:
Find out more about the Week 5 Challenge on the overview blog post.
The winning solution, was submitted by Patrick Flynn, just 3 hours and 18 minutes after the challenge was posted. Patrick provided me with the following steps, and TSQL code to back up the steps:
The process was
(a) Restore two copies from backup (Old backup has 400 Customers and 1622 Orders)
(b) Use the supplied MDF, LDF and NDF to hack attach to instance
(c) Try using tail-log backup but log chain broken also as errors in Boot page (1:9) unable to use all files
(d) Instead using original backup replace only log file and ndf file (containing user data)
(e) After switching to emergency mode found errors in Orders table (1:175) but this does not contain new rows
(f) Able to select the newest 181 rows and insert into original orders table
Final Status was
Orders = 12803 rows
Customers = 400 rows
No corruption remaining
Here is the exact TSQL code that supported that solution.
Read More »Week 5 – Winning Solution – Database Corruption Challenge
As the weekend approaches and we head for another Database Corruption Challenge (DBCC) I want to remind everyone who is interested of being notified of… Read More »Another Corruption Challenge This Weekend.