"R Baker" <nospamx@nospamx.com> wrote in message
news:%23xkAXOnYDHA.2204@TK2MSFTNGP12.phx.gbl...
> I have a client that is experiencing repeated non-convergence in one (out
of
> 130) articles in a merge replication database.
>
> Several identical schemas are being subscribed to in this environment and
> the same article is causing trouble in each one.
>
> Here are some common elements:
>
> 1. The article in question has a "FOR REPLICATION" trigger on it, but it
> doesn't update this particular table.
>
> 2. Replication for these subscriptions is being done via a merge agent
> rather than the SQLMerge. I haven't identified an instance where the same
> article is having trouble when the SQLMerge object is being used.
>
> 3. No conflicts have been reported on the table.
>
> 4. The GUID's of the non-converged rows DO match.
>
> Can someone suggest how I might do some more sleuthing to see why the
> updates to this table are not coming across? (e.g. peeking into the
metadata
> tables somehow -- perhaps a reference to an article as to how to interpret
> the lineage or generation data to make sense of this). Or, is there some
> known problem that has yet to find it's way into an SP?
>
>