I guess that's one of the classical (legacy?) SQL Remote questions.
Usually, the operation from the sender is not sent back to that remote, in order to prevent send/resend cycles. That's a reasonable think, as it would usually be no good if the just INSERTed row would bounce back as an additional INSERT:)
However, there seem to be a few exceptions:
While re-thinking about an ASA 126.96.36.19974 SQL Remote setup, I have found unsure as when exactly such re-sending takes place.
So I would greatly appreciate more insight here - to fill/correct this list of exceptions:)
Source: Partly the NG entry "Re: Can Update Publication force an update?" by Rob Waywell, cf.news://forums.sybase.com:119/r9Unc0qM$GA.email@example.com.
asked 22 Feb '10, 16:54