O'Reilly logo

Microsoft SQL Server 2012 Internals by Bob Beauchemin Kalen Delaney Conor Cunningham, Jonathan Kehayias, Benjamin Nevarez, and Paul S. Randal

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

Consistency checking

Although SQL Server itself doesn’t cause database corruptions, I/O subsystems—all the software and hardware between the SQL Server buffer pool and the metal oxide of the disk drives or memory chips of the solid-state drives—do cause the overwhelmingly vast majority of corruptions. For this reason, the common wisdom is that performing regular consistency checking is prudent because all database servers have an I/O subsystem of some sort. The definition of regular, in this sense, really depends on the situation and how confident you are with the integrity of your I/O subsystem. In general, performing a consistency check once a week would be acceptable. If resource constraints are an issue in your environment, consider restoring ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required