Comments (9)

  1. In case we do not have the resource DB files backed up but find ourselves in need of recovery, then we could also use files from a different instance which is at the same version and has the same features installed on it.

    1. Thanks for calling that one. I thought about mentioning it while writing it, but then I started wondering if it was a supported solution and did not want to call it out without knowing that it wouldn’t make their installation unsupported. I don’t think it would but want to be sure before publicly recommending it.

  2. Appreciate your effort Robert. I Really enjoyed the whole series!

    1. Thanks sabuv! Later this week, I will post a “round-up” post and put all 31 days into a downloadable pdf.

  3. […] Follow this link: Day 31 of 31 Days of Disaster Recovery: Backup and Restore of the … […]

  4. Another great article. Thanks. Full Disclosure. I’ve never backed it up.

    1. Thanks! Not many people do.

  5. hi Robert.
    I have learned a lot from you. Good job and thanks for sharing the knowledge.
    I think the you forgot one thing or maybe i’m wrong. What happen if you move the master file to a new location??? is resource db depends on the master as too???

    Thanks you once again.

    1. Hi Ramon. It depends on the version of SQL Server you’re using. Older versions of SQL require that the resource db and master db files be in the same location. Newer version use a specific location for the resource db file. I don’t recall off of the top of my head which version that changed.

      My advice in this post doesn’t talk about moving the resource db or master db. Backing up and restoring the resource db is a totally separate issue from moving databases.

Leave a Reply