Log-File move

  • Dear all,

    just after any opinions on the following procedure for moving a log-file to new location for SQL2K replicated DB;

    1) Backup DB

    2) Backup log-file

    3) Stop replication

    4) Shrink log-file (so move is quicker)

    5) Script out replication objects

    6) Drop subscriptions

    7) Delete Publication

    8) Disable backup jobs

    9) Disable DB for replication

    10) Make note of DB ID

    11) Detach DB

    12) Once detached, move physical log file to new location.

    13) Re-attach DB, pointing to the new location of the log file

    14) Check DB ID is as before and re-enable DB for replication

    15) Recreate Publication (from script saved earlier)

    16) Recreate Subscriptions

    17) Start Snapshot agent(s)

    18) Start Synchronising

    19) Re-enable backup jobs

    Anything else i should be aware of?

    I realise there are some short-cuts (Andy Warren's article being one) but i'd rather not take that kind of risk on a production DB.

    Many thanks in advance

  • Just a question.

    If you would like to restart the snapshot, do you really need to do all backups on the subscriber side?

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

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