Mother object

[NightSkull]

I've been having an intermittent error... several transactions are called using a mother object... due to some deadlocks while accessing tables on the db, sql server automatically kills one of the processes involved in the deadlock... all transactions within the mother object should have been rolled back... but somehow, one the transactions is not rollback while the rest do... is there any property i forgot to set?... is there any explanation for such behavior?...

 

[DASMAN]

hi,
both object should support transaction* and have one to use it.

* if both support transaction and are called from a component that not support or from a base client the transaction will not by created.
Try setting your mother object to transaction required and the other to support or required.

DAS

 

[zeevgetner]

you assume that in the situation of deadlock all transactions are roled back, but it is not true because sql-server chuses one o the transactions to be the dead-lock victim and it rolls it back, and the otheronce continue.

the solution - avoid deadlocks