Hi,
I'm having a headache with the following questions weavering around...Hope that someone can help me with the answers.
1) I've implemented a immediate updating transactional replication on 2 servers. The loopback detection is also set to true. Under normal circumstances, when there is an transaction at the subscriber, it should be replicated to the publisher. However, this was not the case here. There were some transaction in the subscriber, but they were not replicated to the publisher. Is it because of the "loopback detection" option?
2) If a bi-directional transaction is to be implemented as according to the BOL, there will be 2 distributors. When a publisher has a transaction, it will be replicated to the subscriber. When the subscriber commit the transaction, will the transaction be sent back to the publisher's distribution database? or will the distribution agent at the subscriber will know that it originated from the publisher and will not sent it to the publisher?
Pls pardon my long msg. Any advice is welcome.
no advice available?|||Did you set up immediate updating subscriber using the UI/wizards? If so, do you see the triggers on the subscriber tables, they should be named something like trg_MSsync_ins_<table name>, trg_MSsync_upd_<table name> and trg_MSsync_del_<table name>.
What I'd do is profile the subscriber and publisher when making changes at subscriber to see what code of the trigger is getting executed.
No comments:
Post a Comment