Service Broker proper usage ?

[Alfred]

Even though it came out with SQL server 2005, I am new to this concept...

I have a process whereby I would like to accomplish the following...

The setting includes many client workstations using a VB.net application to
communicates with a database via ADO connections.

The workstations will be adding "transactional" information into some sql
server tables.

Been there, done that... so far, so good...

Unfortunately, that is only half of the "transaction"...

Once the first half of the transaction has been successfully committed to
the sql tables, elements of this data must then be used to create the second
half of the transaction which includes pushing it into an ERP system (via a
COM oriented procedure). Actually, what I would like to do is invoke a
second VB.net program using data from the sql tables. Or maybe just vb.net
code ?

All the example I have seen thus far show TSQL being used to update a table.
Can you actually run a vb.net program using the service broker ? Should
you ? Any online samples detailing this ? Good books illustrating this ?

I AM interested in invoking the second half of the transaction as soon as
possible following the first half of the transaction.

However, I am not interested in reversing the first half of the transaction
if the second half of the transaction is not successful.

Any advice on specifics would be appreciated !

[Adam Machanic]

Google "service broker external activation" and you'll be most of the way
there.

--Adam Machanic

"Alfred" <aaanone> wrote in message
news:44adnRSGyfaorQrW...@giganews.com...

[Alfred]

Thanks !

I am seeing conflicting info on the topic...

Do you know if this is available in SQL server 2005 ? Or is it only
available in 2008 ?

"Adam Machanic" <amREMac...@gREMmOVEail.com> wrote in message
news:%23NIntGM...@TK2MSFTNGP04.phx.gbl...