I have two long running transactions (A (for an Insert)) and (B( for an
Update) inside of a single long running transaction.

I have placed a compensation on transaction A that does a delete operation
for the previously inserted record. For some reason, I get the insert just
fine and then it falls right into the compensation and executes a delete.

I thought that the compensation would not be called unless the Update failed
and the primary transaction rolled back the changes. It looks like it runs
every time. Is this correct?

Norton

[ Post a follow-up to this message ]

Finally figured out everything was being called in the right order.

My orchestration was jumping to transaction B and back so fast I couldn't
see what it was doing. I eventually had to add an expression shape in the
middle with a breakpoint just so I could catch it while debugging the
orchestration.

Norton
"TheNortonZ" <thenortonz@hotmail.com> wrote in message
news:eCncAdWtEHA.2800@tk2msftngp13.phx.gbl...
>I have two long running transactions (A (for an Insert)) and (B( for an
>Update) inside of a single long running transaction.
>
> I have placed a compensation on transaction A that does a delete operation
> for the previously inserted record. For some reason, I get the insert just
> fine and then it falls right into the compensation and executes a delete.
>
> I thought that the compensation would not be called unless the Update
> failed and the primary transaction rolled back the changes. It looks like
> it runs every time. Is this correct?
>
> Norton
>

[ Post a follow-up to this message ]