Post reply

Merge Replication: conflict_ tables and periodically appearing rows

  • December 7, 2005 at 12:28 pm

    #96060

    BOL effectively states that when a conflict occurs, the loser is written out to the conflict_ table.

    That all makes sense. Problem is, BOL doesn't tell me why those rows periodically dissappear.

    Anyone know what is going on? Some conflict_ tables will have a few hundred rows in them, etc - then a few hours later the conflict losers are gone.

    BOL doesn't seem to be painting the whole picture. Does SQL Server just keep trying the conflicts until everything is jiggy? or does some cleanup agent come by and sweep them?

    I'm going to be looking at tweaking the merge replication agent to avoid these conflicts, which are just FIFO problems - so I'm not worried about the CAUSE of the rows appearing - just wondering WHY they dissappear, and if that's normal/expected behavior. (And if so, what is going on?)

    Thanks in advance.

  • December 12, 2005 at 8:00 am

    This was removed by the editor as SPAM

  • December 13, 2005 at 6:52 pm

    #609378

    yep,

    are you using a pocket device or anonymous publication?, a snapshot (or a task in the snapshot process) may clear out these tables hence them dissappearing..

    fun and games

    HTH


    ------------------------------
    Life is far too important to be taken seriously

Viewing 3 posts - 1 through 2 (of 2 total)

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