Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

Transactional replication issues Expand / Collapse
Posted Sunday, April 14, 2013 3:28 AM


Group: General Forum Members
Last Login: Monday, June 9, 2014 9:22 AM
Points: 11, Visits: 373
Hello There,
I am new to this forum,
Could anyone help me with this questions please.
I am working in retail industry and has some doubts relating to this topics.

Our company has 100 stores and the data has to be replicated to the main subscriber server from all the 100 publishers. We have set up a transnational replication with one distributor. In a region for some 15 stores we have network issues, the data was not replicated to the main server.

1.How can we replicate the data when the network is back to normal ?
2.If any of the remote server gets crashed, how do we restore the publication after the server gets normal (what is the procedure to follow) ?

- How do we apply changes to remote servers using Transactional Replication

· If there was an issue with a certain server, how do we stop and restart replication

· How do we apply changes to a replicated server
Post #1442094
Posted Thursday, April 18, 2013 12:53 AM



Group: General Forum Members
Last Login: Tuesday, June 21, 2016 10:46 PM
Points: 128, Visits: 601
This could you help you to understand the setup and process.

Some more information from external blog -


- Win
"Dont Judge a Book by its Cover"
Post #1443622
Posted Monday, April 22, 2013 5:06 AM


Group: General Forum Members
Last Login: Thursday, October 27, 2016 5:00 AM
Points: 485, Visits: 2,131
When you talk of an issue with some server, I will say that when it comes up replication will assume automatically from where it left off.

Lets say that the publisher server is down, so it means no new data changes are going to occur and the distributor will have no work to do until it comes up and subscriber's data will be the same when the publisher had gone down. So just focus on getting the publisher up and replication will catch up on its own.

If distributor server is down then the publisher will keep a track of all 'to-be-replicated' commands in its log file and when distributor comes up, log reader agent will scan all the logs and send the information to the distributor and then only changes to subscriber will start. so again, just focus on getting the distributor server up.

If subscriber goes down, you will have all changes kept in distributor , waiting to be propagated. so again, focus on getting subscriber up,.

For higher network latencies, try using different agent profile for log reader and distributor agent with more time-out values, small commits etc.


Post #1444924
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse