0

I am trying to have a trigger fire when the Merge agent\user insert\delete\update data. The trigger inserts data into a log table. I don't want to use NFR (Not For Replication) because I need that the trigger will fire when merge agent inserts data.

At first, I thought it was the problem with the replication but when I change the triggers into NFR everything was working fine. (which is not good because I need them to fire when the merge agent inserts data as well).

Then I thought it was a problem with the triggers but when I insert\update\delete data using t-sql the triggers are working fine.

The problem is that the data is not synchronized as it should be in merge replication. When I update a column, I can't see it on the other database unless I'm changing the trigger into Not For Replication or disabling them.

Any ideas?

  • 1
    What does NFT mean? I have read and re-read your post but I still don't get a clear picture of what happens, etc. Can you elaborate? – Tibor Karaszi Jan 8 at 14:19
  • I think NFR = Not For Replication :) – sepupic Jan 8 at 14:25
  • @TiborKaraszi I don't think the problem was described anywhere in the post. It's not just you. – Jacob H Jan 8 at 14:49
  • NFR = Not For Replication :) – DnL Jan 8 at 15:50
  • The problem is that the data is not synchronized as it should be in merge replication. when I update a column i can't see it on the other database unless i'm changing the trigger into Not For Replication or disabling them. – DnL Jan 8 at 15:55

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.