Post reply

Automated 24 hour old copy of a live database required

  • February 16, 2015 at 4:03 am

    #304382

    Firstly let me apologise, I am no means a DBA so if my question seems basic then I am sorry!

    I have a requirement that a copy of the live database be copied to another server, but be 24 hours behind the live database. This is so a 3rd party can access data that is reasonably up to date but without touching the live database. My thinking was to script an automatic restore but after reading a few articles it seems replication may provide a better solution?

    Not having replicated a database that needs to be 24 hours behind the live database (on another instance by the way), are there any pointers anyone can give me as to where to start? The database concerned is relatively small.

    Many thanks

    Jas

  • February 16, 2015 at 4:13 am

    #1777780

    Backup/restore strikes me as the easiest solution.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • February 16, 2015 at 9:03 am

    #1777849

    I'll second Gail's recommendation. If it's a huge database, then something a bit more complicated might work better once it's setup.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 3 posts - 1 through 2 (of 2 total)

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