SQL Server Database Corruption, Part XIII: RECAP

One of the things I wish I had done a bit better in my previous 'series' of posts on SQL Server database corruption was provide better links and cohesion between posts—or a 'table of contents' at the top or bottom of each post—just because I always appreciate similar efforts when I stumble upon a series of posts via a set of keywords I’m searching for and so on.

SQL Server Database Corruption Series – All Posts

And while I’m sure anyone interested in this topic can easily navigate through past posts, I figured it would just be easier (and hopefully beneficial) to provide a 'round up' of all of these posts in a single location. So here goes.

  • Part I: What is Corruption. An overview of what corruption is, how it is caused and why its something DBAs really DO need to account for.
  • Part II: Simulating Corruption. An example of how to gain hands-on familiarity with what corruption looks like and how it ‘works’.
  • Part III: Preventing Corruption. An overview of how preventing corruption isn’t possible – along with an overview of what that means from a continuity standpoint in terms of responding to corruption when it happens.
  • Part IV: CHECKSUM Page Verification. An overview of why all databases should be set to CHECKSUM Page Verification as a means of helping enable early detection of corruption.
  • Part V: Storage Problem Alerts. A step by step overview of how to enable alerts for situations where SQL Server detects problems with the underlying storage system.
  • Part VI: Regular Corruption Checks. Guidance on how to set up and best use regular DBCC CHECKDB() checks of key production databases.
  • Part VII: Backups. Overview of how to include backups in the process of regularly checking for corruption by means of the CHECKSUM option.
  • Part VIII: The Importance of Backups. Overview of how backups are essential in responding to and recovering from corruption of all sorts and types.
  • Part IX: Responding to Corruption. A comprehensive check-list of what to do WHEN corruption occurs.
  • Part X: Page Level Restore Operations. A set of step by step instructions that help showcase the process of using Page Level restore operations to respond to 'small' amounts of corruption.
  • Part XI: Full Recovery Operations. A set of step by step instructions that outline the order of operations to use when recovering from large amounts of corruption or corruption against key pages.
  • Part XII: Recovery Sample. A soup-to-nuts set of examples and T-SQL that you can use to simulate the generation and correction of corruption within your own environment.

Please or Register to post comments.

What's Practical SQL Server?

Practical advice, insight, and help for core SQL Server considerations.


Michael K. Campbell

Michael K. Campbell is a contributing editor for SQL Server Pro and Dev Pro and is an ASPInsider. Michael is the president of OverAchiever Productions, a consultancy dedicated to technical evangelism...
Blog Archive

Sponsored Introduction Continue on to (or wait seconds) ×