When Database Corruption Strikes
Your database is running fine month after month with no problems. 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 two 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 can do to protect yourself when corruption strikes. Learn how to avoid making things worse, and how to protect your data if things do get worse. You will leave with a checklist of steps to use when you encounter corruption. By the end of this session you will be ready to take on corruption, one database at a time.
Steve Stedman is the leader of the Bellingham PASS Chapter in WA, USA. Steve runs his own SQL consulting firm, Stedman Solutions, LLC. He has almost 30 years of programming and SQL experience. He has written the book on SQL Common Table Expressions. He teaches, speaks at conferences, writes, and has taught SQL server classes at Western Washington University. Steve has previously spoken at PASS Summit, TechEd, DevTeach Vancouver, and many SQLSaturdays.