Post reply

Data not replicating sometimes..

  • February 28, 2009 at 7:09 am

    #206467

    Hi everyone.

    I have a problem with our merge replication, there are some data which were not replicated when it created on one server, some times modifications also not synched to other servers. what could be the possible causes?

    Please guide me or suggest any solution for this.

    Thanks,

    Noman

  • February 28, 2009 at 7:47 pm

    #951558

    Hello,

    Are you getting any related errors in the Windows Event Logs, or displayed in the Replication Monitor?

    If it is related to (Merge) Conflict Resolution then this BOL Topic shows you where the conflicts are logged: How Merge Replication Detects and Resolves Conflicts

    Regards,

    John Marsh

    www.sql.lu
    SQL Server Luxembourg User Group

  • March 1, 2009 at 4:56 pm

    #951624

    Did You check if the rows that are getting updated are satisfying the Filter conditions?.

    Is the Distribution job running?

  • March 4, 2009 at 1:46 am

    #952943

    Thanks, but conflicts have resolved on daily basis. but still some data missed which is also not the part of conflicts.

    any possibility of msmerge_contents table having many rows in it??

    Thanks,

    Noman

  • March 5, 2009 at 5:26 am

    #953928

    Hello again,

    Are the Replication updates being delivered to the Target Server? If so, then are there any triggers on the Target Tables that might be reversing the updates?

    Regards,

    John Marsh

    www.sql.lu
    SQL Server Luxembourg User Group

  • March 5, 2009 at 7:23 am

    #954010

    Thanks John,

    Although we have the triggers on that tables but i cheked all again we have the same schema where these triggers are inserting actually.

    what could be the other possibility for such behavior, i did conflict resolution daily and still many records not replicating. i again update that record, it will replicate in next coming batch.

    seems triggers not fired all the time.. or what??

    Thanks,

    Noman

  • March 14, 2009 at 7:31 pm

    #959823

    Hello Norman,

    Apologies for the delayed response, but I have been on holiday for a few days.

    Did you ever get to the bottom of this?

    As you have Triggers on the target tables, would it be possible to temporarily add auditing to them i.e. write the record’s PKs to an audit table each time the Triggers are called? That way you would be able to tell if it is or is not the Triggers that cause your issue.

    I would really expect SQL Server would be writing errors somewhere (in the Event Log or Replication Monitor) if the root cause was the Replication.

    Regards,

    John

    www.sql.lu
    SQL Server Luxembourg User Group

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply