It's not an issue with the replication software. The reason the parts of the
transaction are written out of order is that the original system that writes
them in the first place makes no guarantees as to the order of writing.
So basically my question is whether a trigger that runs a full aggrega
Subject changed to describe the problem. Reply in-line.
On 09/04/2012 07:57 PM, Herouth Maoz wrote:
The issue is that when an insert or an update is fired, I can't say
whether all the segments of the same transaction have been written yet,
and if only some of them were written, there is no guar
