Home Forums SQL Server 2016 SQL Server 2016 - Administration Tlog backups - indicate no data change RE: Tlog backups - indicate no data change

  • March 24, 2017 at 4:32 pm

    #1934910

    sqlguy80 - Friday, March 24, 2017 12:38 PM

    Hi,

    For the db backup restore project moving ~ 1200 dbs ( some vldbs 500 GB as well )  from 32 bit  sql server 2008 old to 64 bit new hardware  sql server 2014  after the full backup is taken at  soucre and restored WITH NO RECOVERY

    After the final cut off, is it ok to just 2 Transaction Log backups and once the size of T log backups are same, I assume it confirms no data has changed, at that point

    just restore the 2 Tlog backups with no recovery and last step restore database with recovery . CORRECT? or did I miss anything?

    Thank you

    My recommendation would be to do a "Tail Log" backup to set the source DB to a "recovery" state so that no new transactions can be inserted, deleted, or updated.

    --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)