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


Best replication solution for poor connectivity scenario


Best replication solution for poor connectivity scenario

Author
Message
S_Kumar_S
S_Kumar_S
SSCrazy Eights
SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)

Group: General Forum Members
Points: 8128 Visits: 1151
Hi All
I am struggling to configure transnational replication between some retail stores and head quarter. Some of the retail stores doesn't have very good connectivity and the link might be down for few hours. This breaks down my replication. I am re initializing my replications without snapshot as it is very slow if I take a snapshot and apply that again.
What I am looking for is a solution for this scenario, so that even if the network is down for few hours, the replication again picks up. I don't want the agents to stop after several retries.
Is there any setting that I should do so that replication doesn't stop after several retries.
thanks
SK

Online Trainer For SQL DBA and Developer @RedBushTechnologies with 16 yrs exp.
TheSQLGuru
TheSQLGuru
SSC Guru
SSC Guru (121K reputation)SSC Guru (121K reputation)SSC Guru (121K reputation)SSC Guru (121K reputation)SSC Guru (121K reputation)SSC Guru (121K reputation)SSC Guru (121K reputation)SSC Guru (121K reputation)

Group: General Forum Members
Points: 121688 Visits: 8989
S_Kumar_S - Wednesday, February 7, 2018 10:47 PM
Hi All
I am struggling to configure transnational replication between some retail stores and head quarter. Some of the retail stores doesn't have very good connectivity and the link might be down for few hours. This breaks down my replication. I am re initializing my replications without snapshot as it is very slow if I take a snapshot and apply that again.
What I am looking for is a solution for this scenario, so that even if the network is down for few hours, the replication again picks up. I don't want the agents to stop after several retries.
Is there any setting that I should do so that replication doesn't stop after several retries.
thanks
SK

Consider removing transactional replication and switching to log shipping to get your data to a central server. From there you can massage/copy it to a mother-ship database as needed. I have used this countless times for clients over the last 25 years of consulting on SQL Server.

Replication is just a mess IMNSHO.


Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
S_Kumar_S
S_Kumar_S
SSCrazy Eights
SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)SSCrazy Eights (8.1K reputation)

Group: General Forum Members
Points: 8128 Visits: 1151
TheSQLGuru - Thursday, February 8, 2018 9:22 AM
S_Kumar_S - Wednesday, February 7, 2018 10:47 PM
Hi All
I am struggling to configure transnational replication between some retail stores and head quarter. Some of the retail stores doesn't have very good connectivity and the link might be down for few hours. This breaks down my replication. I am re initializing my replications without snapshot as it is very slow if I take a snapshot and apply that again.
What I am looking for is a solution for this scenario, so that even if the network is down for few hours, the replication again picks up. I don't want the agents to stop after several retries.
Is there any setting that I should do so that replication doesn't stop after several retries.
thanks
SK

Consider removing transactional replication and switching to log shipping to get your data to a central server. From there you can massage/copy it to a mother-ship database as needed. I have used this countless times for clients over the last 25 years of consulting on SQL Server.

Replication is just a mess IMNSHO.

Thanks for your valuable advice Kevin. I'll surely give it a consideration....replication is really giving me nightmares....


Online Trainer For SQL DBA and Developer @RedBushTechnologies with 16 yrs exp.
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