Understanding destinations that remove rows

If the destination system processes the data and then removes all replicated rows, KeyTable replication may not work correctly. There won't be any errors generated indicating a problem since it will have successfully updated 0 rows, but the update will not get transferred.

Follow the instructions depending on your circumstance.

• If your KeyTable is populated using DPFill stored procedures: In the DPFill caller, use S instead of U, or in the DPFill procedure change an @type of U to S. The Synchronize type will insert the row if it does not already exist.

• If the KeyTable is populated using triggers, then change op=20 to op=40.