Comments on: Statistical Sampling for Verifying Database Backups https://thomaslarock.com/2010/05/statistical-sampling-for-verifying-database-backups/ Thomas LaRock is an author, speaker, data expert, and SQLRockstar. He helps people connect, learn, and share. Along the way he solves data problems, too. Sat, 10 Feb 2018 17:49:09 +0000 hourly 1 https://wordpress.org/?v=6.7.2 By: Upgrading to SQL Server 2016, Part Three | Malaysia Software Reseller | Dealer | PCWare2u https://thomaslarock.com/2010/05/statistical-sampling-for-verifying-database-backups/#comment-16083 Thu, 03 Aug 2017 21:24:27 +0000 http://thomaslarock.com/?p=2548#comment-16083 […] That’s right—create backups. Right now. Before you do anything else. After all, you’re a DBA and backups should be in your DNA. You should have taken one prior to the start of any upgrade or migration, and you had better take one right now, and again before you turn the database over to end-users. Also, you should save any output from the items listed here, as doing so could prove helpful should something go awry later. And don’t forget to make sure your backups are good! […]

]]>
By: Upgrading to SQL Server 2016, Part Three – CHB Blog https://thomaslarock.com/2010/05/statistical-sampling-for-verifying-database-backups/#comment-16080 Thu, 03 Aug 2017 08:09:42 +0000 http://thomaslarock.com/?p=2548#comment-16080 […] That’s right—create backups. Right now. Before you do anything else. After all, you’re a DBA and backups should be in your DNA. You should have taken one prior to the start of any upgrade or migration, and you had better take one right now, and again before you turn the database over to end-users. Also, you should save any output from the items listed here, as doing so could prove helpful should something go awry later. And don’t forget to make sure your backups are good! […]

]]>
By: Upgrading to SQL Server 2016, Part Three https://thomaslarock.com/2010/05/statistical-sampling-for-verifying-database-backups/#comment-16079 Thu, 03 Aug 2017 01:24:47 +0000 http://thomaslarock.com/?p=2548#comment-16079 […] That’s right—create backups. Right now. Before you do anything else. After all, you’re a DBA and backups should be in your DNA. You should have taken one prior to the start of any upgrade or migration, and you had better take one right now, and again before you turn the database over to end-users. Also, you should save any output from the items listed here, as doing so could prove helpful should something go awry later. And don’t forget to make sure your backups are good! […]

]]>
By: Upgrading to SQL Server 2014: A Dozen Things to Check - SQLRockstar - Thomas LaRock https://thomaslarock.com/2010/05/statistical-sampling-for-verifying-database-backups/#comment-12691 Thu, 26 Mar 2015 15:20:37 +0000 http://thomaslarock.com/?p=2548#comment-12691 […] You’re a DBA. Backups should be in your DNA. You should have taken one prior to the start of any upgrade or migration, and you had better take one right before you turn that database over to your end users. Also, you should save any output from the items listed here, as it could prove helpful should something go awry later. (bonus item – make sure your backups are good!) […]

]]>
By: Upgrading to SQL Server 2014: A Dozen Things to Check - SQL Server - SQL Server - Toad World https://thomaslarock.com/2010/05/statistical-sampling-for-verifying-database-backups/#comment-10976 Tue, 03 Jun 2014 23:01:25 +0000 http://thomaslarock.com/?p=2548#comment-10976 […] You’re a DBA. Backups should be in your DNA. You should have taken one prior to the start of any upgrade or migration, and you had better take one right before you turn that database over to your end users. Also, you should save any output from the items listed here, as it could prove helpful should something go awry later. (bonus item – make sure your backups are good!) […]

]]>
By: Shaun https://thomaslarock.com/2010/05/statistical-sampling-for-verifying-database-backups/#comment-1462 Wed, 19 Jan 2011 17:17:54 +0000 http://thomaslarock.com/?p=2548#comment-1462 I like this article, but it is of real limited use to anyone trying to implement it in their own environment because you don’t mention how your sample size (n = 3000) is used. I’m guessing it is involved in getting the magic 1.96 number, but unless we know how, there is no way the reader can use this method to determine how many backups they need to test in their environment. (Unless they also happen to be responsible for 3000 databases as well.)

]]>