Paul’s name should be familiar to denizens of the SQL Server blogosphere. Along with his wife, Kimberley Tripp, he’s a principal of SQL Skills (home also to the redoubtable Bob Beauchemin, with whom I share a birth date of significance to SQL Server aficionados); given that his history includes authorship of DBCC in SQL Server 2000 and major components of DBCC in SQL Server 2005, the name of his blog is among the great puns out there: In Recovery... | Paul S. Randal on SQL Server.
Paul’s a great guy, and if you haven’t caught one of the presentations he and Kim give, you’re definitely missing out. These folks are two of the finest SQL Server presenters in the world. No wonder they’re found at the center of the MCA and MCM Database programs.
Paul’s blog is always a technical cornucopia; recently, he got the inspiration to augment his technical posts with surveys of his community (brilliant, Paul! I wish I’d thought of that!). His first one is a doozy: How often do you validate your backups?
- Almost twenty-five percent of respondents never validate their backups! Huh? Paul wisely quotes Kim, and I’d like to reinforce her statement here: you don’t have a backup until you’ve restored it.
- Forty-one percent of respondents regularly or occasionally validate their full backups (but not differentials or logs!).
- Twenty-eight percent of respondents regularly or occasionally validate their full backups, their differentials, and their logs.
If these statistics hold across the general user base, many of you may be working without a net. There’s obviously lots of work we can do here, and as Paul wisely points out in his article (which you really should read in its entirety), your high availability/disaster recovery plans should never rely solely on backups.
Paul’s second survey pertains to index maintenance. You can participate here.
Thanks, Paul, for the thought-provoking statistics and sage counsel.
this copyrighted material was originally posted at http://blogs.technet.com/wardpond.
the author and his employer are pleased to provide this content for you at that site, and via rss, free of charge and without advertising.
the author welcomes and appreciates links to and citations of his work. however, if you are viewing the full text of this article at any other website, be aware that its author does not endorse and is not compensated by any advertising or access fees you may be subjected to outside the original web and rss sites.