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 8.0.3.5574 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.268@forums.sybase.com. |
Just to add: I would also like to know if there is a need for something like a small "SQL Remote knowledge base" here. SQLA might be more helpful for such questions than those old NG topics...
@Volker: Feel free to post ANYTHING related to SQL Remote... copy and paste from old newsgroup topics is OK with me.
@Volker: Small world, I just spent the morning at a client site trying to resolve a funky SQL Remote 8.0.3 issue involving missing log files. Alas, the solution was the most-hated "re-extract".