Best replication solution for poor connectivity scenario

  • 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 18 yrs exp.

  • 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

  • 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 18 yrs exp.

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

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