O'Reilly logo

Tribal SQL by Matt Velic, David Tate, Shaun J Stuart, Wil Sisney, Mark S Rasmussen, Bob Pusateri, Dev Nambi, Colleen Morrow, Stephanie Locke, Chuck Lathrope, Tara Kizer, Kevin Feasel, Diana Dee, John Barnett, Dave Ballantyne

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

Verifying Backups Using Statistical Sampling

Shaun J. Stuart

Your database backups are only valid when you've proved you can restore the database

This little nugget of wisdom should be foremost in the mind of every DBA. Yes, you created the backup using the WITH CHECKSUM option and, once the backup was complete, you ran a RESTORE VERIFYONLY to validate that the backup was good. The problem is that this confirms only that no corruption occurred between the time the SQL Server wrote the data to disk and reading it for your backup. It will not detect any corruption that happened to the data in memory after data was updated, but before SQL Server hardened the data to the database file. In addition, many mishaps can befall your backup files,

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