SQL Server Backup Best PracticesCommented on: 7 years ago
(October 3, 2008)
Why a FULL backup every day? You realize you limit your ability to recover to a certain point of time with every FULL backup you perform. Suppose we need to go back 4 days ago because the...
Pare Down and Power UpCommented on: 7 years ago
(April 15, 2008)
I hope the author can update his article as somethings have changed. Vitesse no longer makes SAS Expanders. And it looks like Supermicro SC933 is a better fit for a 16-bay chassis since the LSI...
Digital Magazine Archives
Browse back issues of SQL Server Pro, from January 2007 through the last issue published in April 2014. Find the back issues here.
Melissa Data's Data Quality Analyst Joseph Vertido explains how Gartner defines the critical data quality steps to prevent bad data from entering your systems in the first place, and then keep it clean over time....More
I’ll sound a bit like Captain Obvious for bringing this up, but it’s important to remember that security encompasses a lot more than protecting sensitive data from the specter of outsider threats like hackers. Properly implemented security policies also account for threat-models that include insiders – or people within your organization....More
There’s simply no way to overstate the importance of regular Transaction Log Backups. Not only do they help protect from disaster, but regular execution of T-Log backups on Full (and Bulk-Logged) Recovery databases helps keep thing “fit and trim”. Most of the time, setting up a Notification for when T-Log Backup Jobs fail is enough to let you know when something goes wrong....More