SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Moving Distribution Database to different server.


Moving Distribution Database to different server.

Author
Message
sejal p gudhka
sejal p gudhka
SSC Veteran
SSC Veteran (214 reputation)SSC Veteran (214 reputation)SSC Veteran (214 reputation)SSC Veteran (214 reputation)SSC Veteran (214 reputation)SSC Veteran (214 reputation)SSC Veteran (214 reputation)SSC Veteran (214 reputation)

Group: General Forum Members
Points: 214 Visits: 236
Hi All,

I have transaction replication with updatable subscription setup and it is running fine for almost 6 months. Distribution database is located at the publisher and it acts as a Distributor.

My company is getting one more sql server and want to implement database mirroring for above two servers participating in replication.Now there is a need to move distribution database to third server.

My concerns is that I would not like to remove replication and reset it up again as for first synchronization it takes around 48hrs and I can't afford that. I would like to know if there is a way to move distribution database to different server without disturbing or minimally affecting replication ?

Any help will be highly appreciated.

Thanks in advance.

Sejal.
sejal p gudhka
sejal p gudhka
SSC Veteran
SSC Veteran (214 reputation)SSC Veteran (214 reputation)SSC Veteran (214 reputation)SSC Veteran (214 reputation)SSC Veteran (214 reputation)SSC Veteran (214 reputation)SSC Veteran (214 reputation)SSC Veteran (214 reputation)

Group: General Forum Members
Points: 214 Visits: 236
Guys,

here is what I have tried out and it worked for me in my senario.

1) Delete publication and subscriptions.
2) Disable publication and distribution.
3) Reset replication and this time move distribution db to another server.
4) Add publication
5) While adding subscription, uncheck initialize to synchronized publisher and subscriber at first shot.

Basically you are removing entire replication setup and resetting it again with distribution database being on another server, but this time you are not setting replication to synchronized database at both end.

Your replication will start working fine immediately since both dbs are all ready in sync. I have test above solution in my environment and now will do the same changes in production.
sejal p gudhka
sejal p gudhka
SSC Veteran
SSC Veteran (214 reputation)SSC Veteran (214 reputation)SSC Veteran (214 reputation)SSC Veteran (214 reputation)SSC Veteran (214 reputation)SSC Veteran (214 reputation)SSC Veteran (214 reputation)SSC Veteran (214 reputation)

Group: General Forum Members
Points: 214 Visits: 236
Hi All,

I did this in my Production Environment and it seems to be working fine....
ramv-224884
ramv-224884
SSC Rookie
SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)

Group: General Forum Members
Points: 40 Visits: 237
Hi Sejal,

One quick question. Did you detach the distribution DB from the current location and attached it at the new location? or Did you use the new Distribution Database in the third server as you recreated the subscription and publication.

I would appreciate your reply...

Thanks,
RV
noeld
noeld
SSCrazy Eights
SSCrazy Eights (10K reputation)SSCrazy Eights (10K reputation)SSCrazy Eights (10K reputation)SSCrazy Eights (10K reputation)SSCrazy Eights (10K reputation)SSCrazy Eights (10K reputation)SSCrazy Eights (10K reputation)SSCrazy Eights (10K reputation)

Group: General Forum Members
Points: 9960 Visits: 2048
This was definitely a "new" distribution database setup.


* Noel
ramv-224884
ramv-224884
SSC Rookie
SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)SSC Rookie (40 reputation)

Group: General Forum Members
Points: 40 Visits: 237
Thanks for you response Noel. Yeah I figured it out after some trials.

Thanks,
RV
mohamed-891698
mohamed-891698
Grasshopper
Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)Grasshopper (19 reputation)

Group: General Forum Members
Points: 19 Visits: 22
I have a replication from db1 in Server A to db2 in Server B. Now I am planning to move the db2 to different server Server C. Is it possible for me to change only the subscriber details in Server A and make the replication works for Server C?
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search