Post reply

Replication DB migration on new sql server 2008R2

  • August 8, 2013 at 2:49 pm

    #275966

    Hello,

    We will be planning to migrate sql 2005 and sql 2008R2 on new windows 2008R2 server, we have one Replicated DB which ones we are subscribing and we don't have any control over publisher.

    Could you please guide me that how can we handle it?

    We are planning to do side by side installation and will be using Backup and Restore method but some worries how we can handle it for Replication DB and which is the biggest DB almost more then 300GB.

    Thanks,

  • August 12, 2013 at 8:16 am

    #1640613

    Any help, please?

    Thanks.

  • August 12, 2013 at 2:07 pm

    #1640703

    We will be planning to migrate sql 2005 and sql 2008R2 on new windows 2008R2 server, we have one Replicated DB which ones we are subscribing and we don't have any control over publisher.

    Could you please guide me that how can we handle it?

    Once you have your new SQL Server 2008R2 server up and running you just need to subscribe to the published database(s).

    We are planning to do side by side installation and will be using Backup and Restore method but some worries how we can handle it for Replication DB and which is the biggest DB almost more then 300GB.

    I'm going to assume that by "Replication DB" you are talking about the subscriber DB -- the DB that is being replicated (not the Distribution DB which stores your replication info).

    Don't restore the replicated DB, this would be a waste of time. Again, you will have your replicated DB once you create a subscription to the publisher. 300GB is fine provided you have the RAM and drive space to support it. The only concern I would have is the time it will take for the snapshot agent to create the new snapshot - this may be time consuming. If possible, make sure that there is no work being done on the published database when you do this.

    Lastly: if you get a chance, take a look at the Stairway to SQL Server Replication[/url] by Sebastian Meine.

    "I cant stress enough the importance of switching from a sequential files mindset to set-based thinking. After you make the switch, you can spend your time tuning and optimizing your queries instead of maintaining lengthy, poor-performing code."

    -- Itzik Ben-Gan 2001

  • August 12, 2013 at 7:19 pm

    #1640758

    Thanks Alan.

    Right, I am talking about Subscriber DB.

    If we get from the another subscription then it will be fine.

    If we get the new subscription then we have to do anything from subscriber side?

    We re thinking that once we can start the subscription for new server then we will turn off the agent while we restore the DB then we will start again o it will pick up from where it's stopped, right?

    Thanks

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

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