We have established a Report server (subscriber) for our
OLTP production database (publisher). Transaction
replication is running between the two databases.
An UPDATE on the OLTP database is triggering a
DELETE/INSERT on the Report database. This DELETE is
causing a FK conflict and results in replication errors.
It appears that if an UPDATE is done on an index key, this
causes a DELETE/INSERT instead of an UPDATE. Is there any
way to handle this without dropping the FKs on the Report
(subscriber) database in replication?
Thanks
Jay,
this is a known issue. There is a solution though:
http://support.microsoft.com/default...NoWebContent=1
hth,
Paul
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment