For such circumstances , you have to look after the below:
- The replication log and see what tables are broken down while replication
- Then investigate why broken down at publisher not subscriber
…Is it some kind of duplication ,Heavy locks on publisher or distributor is not able to connect publisher
- Then you may have a look at conflict resolver that I am forecasting Subscriber is always the winner due to using that
special conflict resolver
named "Subscriber always win" on relevant tables
Kindly check on them and let me know your feedback
Shehap (DB Consultant/DB Architect) Think More deeply of DB Stress Stabilities