Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Replication Migration problem Expand / Collapse
Author
Message
Posted Wednesday, September 25, 2013 2:36 PM


SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: 2 days ago @ 2:58 PM
Points: 97, Visits: 348
I have a 2008R2 environment that I want to migrate to 2012 for replication. The production servers will remain 2008R2 and I want to replicate using a new 2012 distributor to a new 2012 destination. I have over 30 replication jobs to migrate and want to minimize downtime. My original thought was to add new publications to my existing production servers that would point to the new distribution database. From everything I have been able to find out, that is not an option. So, first question, does anyone know of a way to to this? This would be ideal for the new replication.

Failing that, what is the best way to migrate (with least downtime and best possibility for rollback) from the old replication to the new. My original solution was to leave the old replication untouched until I could verify that the new replication was working properly. If I can't have a publisher that points at more than one distributor, then I don't see how I can do that.

This seems like the only thing is to script out all the existing publications /subscriptions, modify them to point to the new servers with new logins etc. Drop all the old publications /subscriptions en masse and recreate them via the script pointing at the new environment. This seems like a fairly high risk maneuver, with little room for mistake or rollback.

Any ideas? I'm sure I'm not the first to do this.

Thanks,
Dave Bennett
Post #1498590
Posted Wednesday, September 25, 2013 3:05 PM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Sunday, September 14, 2014 7:30 PM
Points: 875, Visits: 2,133
So you are replacing both Distributor and subscriber keeping the publisher same ?What is the problem in creating a new publication ?
Post #1498597
Posted Wednesday, September 25, 2013 3:08 PM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Sunday, September 14, 2014 7:30 PM
Points: 875, Visits: 2,133
yeah I see what you are saying. Yeah, I don't think there is a way without dropping the replication. you ve to drop and recreate it.
Post #1498598
Posted Wednesday, September 25, 2013 3:09 PM


SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: 2 days ago @ 2:58 PM
Points: 97, Visits: 348
My problem is that this is live production data. I want to (if possible) have a way to keep the existing publications that feed the current environment up and running while setting up the new publications/subscriptions on the new environment.
Post #1498599
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse