How do Biztalk developers normally handle multiple DB updates from within
.net components that are being called from a Biztalk orchestration?
Receive PO
|
Expression Update SQL Via .Net Method call
|
Expression Update SQL Via another .Net Method call
|
Stop
I need to be able to rollback the transaction preformed in the earlier
stages.
Surly someone in this news group knows the best way of handing multiple DB
updates from within .net components that are being called from a Biztalk
orchestration?
The problem with putting into a store procedure is that all of the
visibility of the process is lost, i.e. I might as well use DTS!
Thanks in advance
Simon
matt
<e...@ee.demon.co.uk> wrote in message
news:444e7f60$0$8021$c3e...@news.astraweb.com...
Thanks matt.
Have you actually used this technique?
Do you know where I could find a example.
Thanks in advanced
Simon
Thanks matt.
I was sure someone must know how to implement transactions in this scenario.
Would you go about it this way?
I am tying to sell the use of Biztalk as appose to the current DTS so the
orchestrations need to be quite visual, i.e. I cannot just locate all the
functionality into a stored procedure.
I was sure someone must know how to implement transactions in this scenario.
Would you go about it this way?
I am tying to sell the use of Biztalk as appose to the current DTS so the
orchestrations need to be quite visual, i.e. I cannot just locate all the
functionality into a stored procedure.
Have you actually used this technique?
Thanks in advanced
Simon
Matt
<e...@ee.demon.co.uk> wrote in message
news:44506678$0$32067$c3e...@news.astraweb.com...
I am facing a similar problem. The only difference is that my COM+
Components and Database Servers are in different domain. I am using the
atomic transaction and trying to pass this to Serviced Components but it is
failing.
Your help to resolve this problem will be highly appreciated.
Thanks in advance
Madhup.
I have used the serviced .net components registered in transaction server,
with multiple SQL statements, as well as multiple oracle statements, both
work when set up correctly as a DTC transaction, within an atomic scope.
EG: 2 separate sprocs are called from BizTalk that do updates, and the 3rd
separate call fails, all 3 roll back.
Works a treat.
"Madhup" <Mad...@discussions.microsoft.com> wrote in message
news:3F1B2435-4D3B-465B...@microsoft.com...