Why subscriber database doesn't change in a two way transactional replication?

Unanswered Why subscriber database doesn't change in a two way transactional replication?

  • Friday, April 29, 2011 9:09 AM
     
     

    I'm doing a two way transactional replication.

    I have a problem, when subscriber database changes the publisher will change but when the publisher database changes the subscriber database doesn't change.

    what can I do?

All Replies

  • Wednesday, July 18, 2012 5:12 AM
     
     

    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