Post reply

Restoring a replicated database to the same server for testing, with another name

  • December 23, 2014 at 1:12 pm

    #293853

    We like to restore a replicated database with multiple dbs, to the same server to test new functions.

    I'm concern if after making a restore to a new db, for example from "dbo.Prod" to "dbo.Test" something will be fail with replication process in the production database.

  • December 24, 2014 at 12:06 am

    #1766297

    Hi,

    What do you mean when you say

    We like to restore a replicated database with multiple dbs

    I am guessing you want to restore a copy of the replicated database on the same instance with a new name. If that is the case.. There is no issue in doing that.

    1. Take a Full backup of the replicated database.

    2. Restore it on the same instance with a new name.

    It will be good to go...!!!

    Hope it Helps...!!!

    Regards,
    Shafat Husain
    🙂
    And Your Lord Never Forgets...!! (64:19 -- Quran)

  • December 24, 2014 at 3:00 pm

    #1766382

    Ah, be careful now. If you have "pass through" views or synonyms to other databases or calls to other production linked servers, the tests that you run on your newly restored "test db" could be making changes to other production systems in a big way.

    My recommendation is that test systems should never reside on the same server as production. There's just too much at risk.

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