distributed transactions

  • Thread starter Thread starter francois
  • Start date Start date
F

francois

I have a set of sql statements (insert, updates) that I want to encapsulate
in a single transaction to be able to rollback the all thing in any case an
exception occurs. If everything works fine then I will commit the all thing
all at once.

The only problem is that the different sql statements are using 2 different
DBs, hence 2 different SQL connections.

My question is how can i have different DB connections using the same
transaction? Maybe someone can forward me to a good resource if it is a
little bit too long to explain in here.

Thanks in advance,
Best regards,

Francois
 
This link is to the roadmap for Enterprise Services:
http://support.microsoft.com/default.aspx?scid=kb;en-us;308672

This one is for COM+ Services, and has links to other topics:
http://msdn.microsoft.com/library/d...y/en-us/cossdk/htm/services_toplevel_8uyb.asp

Enterprise Services is the terminology used if you're developing a
..NET application, and COM+ is the terminology used for older,
COM-based apps. Under the covers it's the same thing -- you host data
access DLLs on a middle tier, and perform your transactions there. The
downside is performance -- there's always a penalty for adding an
additional layer. HTH,

--Mary
 
Here is another link that can help you get started with a hands on example:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/disttranvbnet.asp

The most common set of problems not outlined here are machine configuration
issues in the client and on the server. Make sure you have DTC enabled (not
on by default on win2k3), have the latest OS fixes (Latest service pack for
win2k and QXP6 for windows xp) and that the client and the server can talk
to each other (domain/network issues).
 
Back
Top