Transaction sharing and message integrity

Hi all,

I have a business process that saves data to a DB via a transaction.
The process also calls a BizTalk web service receive location to send
messages. Currently, to prevent the scenario where a message is sent
out BUT the application transaction fails, we write the message itself
to the database and commit the message as part of the application
transaction. This ensures that a message is created reliably when the
application process completes.

Is there a better pattern to handle this scenario? Can I share out the
db transaction to the BizTalk web service to include the MessageBox
also? So that if the application transaction fails, the message is
rolled back from BizTalk?

Thanks!
.

Relevant Pages

  • Re: System.Transactions and database locking.
    ... Scenario: your transaction is open, ... "NOLOCK" and low isolation levels work using option 3; ... There are many scenarios eto cover the permutations of read/write ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Connection.IsolationLevel = adXactSerializable and timeout
    ... I think you misunderstood the scenario or I ... The generation of this new key is not part of the transaction and is not ... unique index on AccountName, for example, because it may be AccountName and ... > Yup, I expect a Counton a non PK column can result in a table lock, ...
    (microsoft.public.data.ado)
  • Re: Transaction when client shutdown
    ... >I check your scenario, and I find that you right. ... is doesn't kill the connection and doesn't kill the process, ... indeed no automati commit or rollback of open transactions. ... transaction remains open and any locks are held until the transaction ...
    (microsoft.public.sqlserver.programming)
  • XA Transactions
    ... the transaction using SQLSetConnectAttr. ... HYC00 'Optional feature not implemented' from the driver. ... and if not what other options do I have to use SQL Server in that scenario? ...
    (microsoft.public.data.odbc)
  • XA Transactions
    ... the transaction using SQLSetConnectAttr. ... HYC00 'Optional feature not implemented' from the driver. ... and if not what other options do I have to use SQL Server in that scenario? ...
    (microsoft.public.data.odbc)