Transactional replication - update does not follow row filter rules
- From: ian.hingley@xxxxxxxxxxx
- Date: 4 Oct 2006 04:13:38 -0700
Hi
I have an issue where inserts follow row filter rules OK, but updates
and deletions don't seem to. I'm using transactional replication.
Let's assume we have a table called Customers with a simple row filter
of
SELECT <published_columns> FROM <<TABLE>> WHERE custkey > 1000
The snapshot and distribution only copies over records with a key
greater than 1000. Correct.
If a record with a key greater than 1000 is updated or deleted, the
transactions are distributed and the same update or deletion appear on
the replicated database. Correct.
However, if a record with a key less than 1000 gets updated or deleted,
there should be nothing to distribute as the row doesn't meet the
filter requirements and doesn't exist in the replicated database. But,
we get the following error:
Error: The row was not found at the Subscriber when applying the
replicated
command.
This sort of implies it is expecting to find a row with the sub 1000
key in the replicated database. Why should this be? I can create a
new distribution agent profile to ignore this 20598 error, but our
customers are not comfortable with this.
Anyone else experienced this? Any resolution? Am I missing something
obvious??
Regards
Ian Hingley
Swift LG Ltd
.
- Follow-Ups:
- Re: Transactional replication - update does not follow row filter rules
- From: Hilary Cotter
- Re: Transactional replication - update does not follow row filter rules
- From: Paul Ibison
- Re: Transactional replication - update does not follow row filter rules
- Prev by Date: Re: Transactional Replication - filtering records in child depending on data in parent table
- Next by Date: Re: Transactional replication - update does not follow row filter rules
- Previous by thread: Remote-Agent Activation
- Next by thread: Re: Transactional replication - update does not follow row filter rules
- Index(es):
Relevant Pages
|