More in Database Backup and Recovery

  • Jun 14, 2012
    blog

    SQL Server Database Corruption, Part XIII: RECAP

    One of the things I wish I had done a bit better in my previous ‘series’ of posts on SQL Server database corruption was provide better links and cohesion between posts—or a ‘table of contents’ at the top or bottom of each post—just because I always appreciate similar efforts when I stumble upon a series of posts via a set of keywords I’m searching for and so on....More
  • bull dog with glasses sleeping on an opened book
    Jun 5, 2012
    blog

    Some Storage Vendors Just Don't Have a Clue About Databases - Redux

    Their storage and backup teams may not know much about databases, but they know when to admit they were wrong....More
  • May 31, 2012
    blog

    SQL Server Database Corruption, Part XII: Recovery Sample 2

    In my last post in this ongoing series on SQL Server database corruption I mentioned that my next post would be to provide a ‘soup to nuts’ sample or example of how you can test corruption and recovery in your own environment – as a means of better getting familiar with exactly what corruption is, what it looks like, and how to address it....More
  • green corrupt data illustration
    May 25, 2012
    blog

    SQL Server Database Corruption, Part XI: Full Recovery Operations 1

    In part 9 of this series on SQL Server database corruption I defined a list of key things to do when responding to database corruption. And in that list of options and operations was the mention that in some cases you may have to revert back to using a full-blown recovery operation – meaning that you’ll need to completely restore your database from scratch....More
  • May 18, 2012
    blog

    SQL Server Database Corruption, Part X: Page Level Restore Operations 1

    In my previous post in my ongoing series on SQL Server database corruption I covered a list of best practices for responding to database corruption when it happens. In that post I mentioned that I’d provide a follow-up post on the specifics of how to execute page-level restore operations from within SQL Server....More
  • magnifying glass looking at the word clue
    May 16, 2012
    blog

    Some Storage Vendors Just Don't Have a Clue About Databases 1

    As database designers we would love to be able to create all our indexes based on ordered values which only increase so that we wouldn't have to worry about index fragmentation. However, we work in the real world....More
  • Apr 26, 2012
    blog

    Is my master database really corrupt? 1

    It’s becoming increasingly common these days for DBAs to want to offload consistency checking of production databases to a secondary server, so that the heavy resource usage associated with running DBCC CHECKDB does not affect the production workload. The practice of verifying backup integrity is also increasingly prevalent....More
  • Apr 17, 2012
    blog

    Avoiding Common SQL Server Backup Mistakes – Follow Up Resources

    In my recent SQL Server Pro Webcast, I blurred through a number of details regarding how to Avoid 5 Common SQL Server Backup Mistakes. Accordingly, I wanted to provide some additional, follow-up, resources to provide some additional context on many of the things that I addressed....More
  • Apr 14, 2012
    blog

    SQL Server Database Corruption, Part IX: Responding to Corruption

    In this post, we’ll look at some best practices for responding to physical corruption when it happens, or is detected....More
  • Apr 11, 2012
    blog

    Enable backup compression by default? 1

    The SQL community was really pleased when Microsoft listened to everyone’s feedback and made backup compression available in Standard Edition of SQL Server 2008 R2 (it was only available in Enterprise Edition in SQL Server 2008). I like backup compression not just for the space savings, but for the time savings during backup and restore operations....More
  • Mar 29, 2012
    blog

    SQL Server Database Corruption, Part VIII: The Importance of Backups

    In Part VII of this series on SQL Server Database corruption we touched upon how backups can be used as an additional means of early detection for corruption – by making sure to validate the checksums of all data being backed up....More
  • Mar 16, 2012
    blog

    SQL Server Database Corruption, Part VII: Backups 1

    In previous posts we looked at how to enable regular checks for corruption and how to set up alerts for IO subsystem problems when they occur. But, as covered previously, one of the key means for properly dealing with corruption is to detect it early – so that you have more options for correcting it at your disposal that you would if it’s allowed to go unnoticed for long periods of time. Consequently, in this post we’ll take a peek at how you can use backups as an additional means of detecting corruption....More
  • Mar 7, 2012
    blog

    SQL Server Database Corruption, Part VI: Regular Corruption Checks

    Previously we looked at how to set up alerts for cases where SQL Server encounters issues with the storage subsystem. Setting those up is a key component to staying alerted to when problems happen – but another great mechanism for detecting corruption early is to set up regular checks for corruption....More
  • Feb 24, 2012
    blog

    SQL Server Database Corruption, Part V: Storage Problem Alerts

    Continuing on from our last post where we looked at setting up CHECKSUM verification as one means of helping more readily detect corruption early-on, we’ll now take a look at how to have SQL Server notify you of any instances where it runs into problems with the IO subsystem....More
  • Feb 21, 2012
    blog

    SQL Server Database Corruption, Part IV: CHECKSUM Page Verification

    In order to be able to better deal with corruption, you need to be able to detect it early. To that end, there are actually a number of different ways to enable early detection of corruption when it happens. Let's look at the use of CHECKSUM Page Verification as the first of these methods....More
  • Feb 9, 2012
    blog

    SQL Server Database Corruption, Part III: Preventing Corruption

    In this post we’ll talk about more about corruption—in terms of addressing how you can prevent it....More
  • Jan 30, 2012
    blog

    SQL Server Database Corruption, Part II: Simulating Corruption

    In my last post I provided an overview of what SQL Server database corruption is—and how it’s almost always caused by problems at the IO subsystem (or disk) level. However, while it’s all fine and well to talk about things in such a theoretical sense, in that post I also mentioned that a great way to get a ‘feel’ for how corruption works is to simulate it a bit on your own. Accordingly, in this post I’ll provide a step-by-step walkthrough of what that looks like by simulating some corruption....More
  • broken data disk
    Jan 27, 2012
    blog

    SQL Server Database Corruption, Part I: What Is Corruption?

    When it all comes down to it there are really only two main things that DBAs need to worry about: making data available to the proper people, and making sure it’s inaccessible to the not-so-proper people. All other considerations are really just appendages to these two concerns....More
  • data center in green, blue and pink lights
    Jan 18, 2012
    blog

    How Can I Use Storage Replication For A Data Center Migration? 1

    The answer to the question here will depend greatly on what storage platforms you have available to you. Assuming that you have some sort of storage array which supports replication to a remote data center you have some pretty neat options available to you....More
  • computer keyboard key labeled backup
    Jan 6, 2012
    blog

    Transaction log corruption and backups 2

    Transaction log corruption is interesting because it doesn’t usually cause any problems apart from failed backups. However, that doesn’t mean it should be ignored....More
  • Jan 5, 2012
    blog

    Should the disks that you are backing up be aligned?

    In short, yes. The LUN or disk which hosts the backups is probably the disk which needs the most write performance....More
  • computer keyboard with red backup key
    Jan 2, 2012
    blog

    Off-Box Backups and Luke-Warm Standby Servers, Part III

    Just having copies of your SQL Server backups in secondary/remote locations is not a disaster recovery plan....More

From the Blogs
business people around a table and laptop
Oct 9, 2014
blog

AlwaysOn Availability Groups and SQL Server Jobs, Part 10: Dynamic Detection Gotcha #3

You can interject a SQL Server Job Step into your Jobs and have this new/injected Job Step do some checking for you. Here's a look at everything that’s involved in such an approach....More
Man holding a piece of paper with the word GOTCHA
Oct 7, 2014
blog

AlwaysOn Availability Groups and SQL Server Jobs, Part 9: Dynamic Detection Gotcha #2 3

Given that a USE statement is parsed before code is actually run, there are a few options that could be used as a around when it comes to detecting whether or not code should be run....More
iceberg
Oct 2, 2014
blog

AlwaysOn Availability Groups and SQL Server Jobs, Part 8: Dynamic Detection Gotcha #1 1

Learn about why the option of dynamically detecting whether or not to run a SQL Server Job at execution time is quite a bit more problematic than you might think....More
SQL Server Pro Forums

Get answers to questions, share tips, and engage with the SQL Server community in our Forums.

Sponsored Introduction Continue on to (or wait seconds) ×