Post reply

Backups of read-only databases

  • May 1, 2018 at 7:02 am

    #334569

    Hello fellows!

    I got a question, here we are making  differentials and logs backups of read-only databases, is this recommended?

    I don't think this is a good practice since these databases are not touched by anyone and are only used for querying, although they aren't taking lot of space i don't think its good, i think is making it harder for my eyes whenever i access these folders and will make it harder in the recovering process..

    Any thoughts are welcomed!

    Thanks!

  • May 1, 2018 at 7:13 am

    #1988758

    Are you performing index maintenance on the databases? I would assume not but I thought I'd ask.

  • May 1, 2018 at 7:20 am

    #1988763

    Beatrix Kiddo - Tuesday, May 1, 2018 7:13 AM

    Are you performing index maintenance on the databases? I would assume not but I thought I'd ask.

    Nop, we are not doing index maintenance to these databases.

    Greetings.

  • May 1, 2018 at 7:52 am

    #1988774

    Superwaffle - Tuesday, May 1, 2018 7:02 AM

    Hello fellows!

    I got a question, here we are making  differentials and logs backups of read-only databases, is this recommended?

    I don't think this is a good practice since these databases are not touched by anyone and are only used for querying, although they aren't taking lot of space i don't think its good, i think is making it harder for my eyes whenever i access these folders and will make it harder in the recovering process..

    Any thoughts are welcomed!

    Thanks!

    Since read-only databases do not change, the only reason for a backup is for recovery purpose. So as long as you have a valid (tested) backup available, no new backup is needed. Of course I would still make new backups and keep multiple copies, but more like once a month instead of daily. That's because a backup could be lost for any reason (like storage corruption or disaster).
    Since the read-only database does not change a differential and log backup would be near empty. If you only make full backups would suffice.

    ** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **

  • May 1, 2018 at 9:10 am

    #1988794

    and will make it harder in the recovering process.

    I don't understand why you'd say that.  The main reason I could see for continuing to do backups of read-only dbs would be make the recovery process simpler.  That is, that all dbs were recovered from the most recent copy, which was always a known time ago.  If you only backup the read-only dbs once a month, say, then you have a different recovery process because you have to find a month-old backup in order to recover that db.

    SQL DBA,SQL Server MVP(07, 08, 09) A socialist is someone who will give you the shirt off *someone else's* back.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply