Wednesday, March 28, 2012

Replication sometimes does not delete all records

Hi all,
I have a following problem with my replication.
I have 3 machines - 1 is publisher and its own distributor, and two are
subscribers. The replication topology model is "central publisher".
The problem concerns the merge replication with filtering (filter is
"2=1"). This replication should take any records inserted into
replicated tables on subscribers and copy them to main server (typical
merge process for new entries). Received rows are checked against the
filter condition and are immediately deleted on subscribers because the
"2=1" condition is impossible.
This is working fine, but sometimes it happens that some rows are not
deleted on subscribers. They are copied properly, but sometimes you can
see the situation when there was 15371 inserts and 15270 deletes. They
are not taken into consideration during the next replication (they are
just left, cluttering the tables on subscribers).
All machines working on sql server 2k with sp2.
Did someone encountered such behaviour? I'm new to replication and I
don't know what can I do to analyse what's going on.
Regards
Xavier
Does anything show up in the conflict viewer?
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||> Does anything show up in the conflict viewer?
No, there are no conflicts shown. There are no errors either. Everything
goes smooth (with one exception).
Regards
|||I'd run a validation to verify everything is working fine.
The record being uploaded/downloaded is likely a metadata record for the system tables.
I am perplexed by your filter. If you are filtering updates coming from your subscriber you are also filtering going to your publisher which begs the question - why are you replicating this table?
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||> I am perplexed by your filter. If you are filtering updates coming from your subscriber you are also filtering going to your publisher which begs the question - why are you replicating this table?
the task i want to achieve is to move the data from distributed machine
to one central server. is there something i missed?
sql

No comments:

Post a Comment