A Step By Step Approach To Recovering The Most Critical SQL Server Databases

Software crashes. WE can't stop that. What WE can do is prepare ourselves through education and practice to be able to act quickly and resolve these critical issues.

In the early days of SQL Server many support calls were server down issues that ended up being bugs in SQL Server. While this still happens, today many of those calls aren't the fault of SQL Server.

For example. On Microsoft's case history of database corruption 99% of ALL database corruption can be traced back to the IO subsystem.

Either way, when SQL Server crashes it can be a traumatic experience for a DBA. If a production box crashes during core hours WE need to know what steps to take to resolve the problem as quickly and as cleanly as possible.