Immediately after initializing a merge subscription, why would the subscriber send back updates?
- From: "Laurence Neville" <laurenceneville@xxxxxxxxxxx>
- Date: Fri, 15 Jul 2005 00:09:33 +0100
I have just set up a merge publication of an entire database. After the
merge agent ran for the first time and the snapshot was applied I ran it
again just to see it say "No data needed to be merged". I was surprised to
see 34 updates and 1 insert being downloaded from the subscriber. I ran the
merge agent a third time and there were yet more updates downloaded.
I am sure no-one was updating the subscriber so where were these coming
from? My only thought is that it might be to do with the triggers that are
on many tables. An update on the publisher end reaches the subscriber and
causes a trigger to fire which inserts or updates another record on the
subscriber which then propogates back to the publisher.
Is there any way to see exactly what the updates are that are being applied,
i.e. what tables and what records? And if it is due to trtiggers firing on
the subscriber, these should be disabled - do I have to manually remove them
all?
.
- Follow-Ups:
- Prev by Date: Re: SQL Server Agent Problem
- Next by Date: log shipping restore fails with no .tuf file
- Previous by thread: How do I tell whats marked for re-initialization?
- Next by thread: Re: Immediately after initializing a merge subscription, why would the subscriber send back updates?
- Index(es):
Relevant Pages
|
