|
Home > Archive > BizTalk Server General > February 2005 > Transaction Types within a Orchestration
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Transaction Types within a Orchestration
|
|
| beewil 2005-02-23, 5:58 pm |
| I can't find any documentation on the transaction type property with in an
Orchestration that explains what happens when it is set to NONE. Currently
I have it set to Long Running, but after reading the performance hit with
this setting I would like to change it. I took out all of the scopes and
tried to change it to Atomic, but I receive an errors saying that I can't
have a send and receive port defined.
What happens if I set the Transaction type to NONE? Is this a good
practice? The orchestration is a real time call to the back end to get data.
There is no reason for retry if it fails and there is code that checks the
return messages's status for error handling.
--
chris wilper
| |
| Bill Ticehurst 2005-02-23, 5:58 pm |
| Hi Chris,
If you don't have any transaction scopes defined in your orchestration and
aren't using features such as compensation, timeouts, exception blocks,
etc... then you won't loose anything by setting the transaction type to
None. I wouldn't recommend setting it to Atomic because you don't want the
perf hit of Long Running - as this is quite likely to cause even more
performance problems.
If you do require guaranteed consistency across different shapes, automatic
roll-back, the ability to define compensation for completed transactions,
etc... then you may want to try and get more familiar with the functionality
and pros and cons of each transaction type. They can add a great deal of
value in many situations, and the perf hit can often be minimal.
Regards,
- Bill Ticehurst [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights
"beewil" <beewil@discussions.microsoft.com> wrote in message
news:A47A9243-BC2A-4C53-83F6-FB30A5D6D590@microsoft.com...
>I can't find any documentation on the transaction type property with in an
> Orchestration that explains what happens when it is set to NONE.
> Currently
> I have it set to Long Running, but after reading the performance hit with
> this setting I would like to change it. I took out all of the scopes and
> tried to change it to Atomic, but I receive an errors saying that I can't
> have a send and receive port defined.
>
> What happens if I set the Transaction type to NONE? Is this a good
> practice? The orchestration is a real time call to the back end to get
> data.
> There is no reason for retry if it fails and there is code that checks the
> return messages's status for error handling.
> --
> chris wilper
|
|
|
|
|