You have three options with transactions:
1. In SQL Server
2. In your code through ADO.NET
3. Via COM+ (Component Services)
With ADO.NET, you can set a transaction that spans multiple databases. You
end up setting up all of the code, which gives you great control, but also
great responsibility. This gets easier with .NET 2.0 next year.
With SQL Server, you will have to link servers to run the transaction. I
have never tried this personally, so I cannot vouch for it, but it makes a
lot of sense.
As a middleware solution, you can create a COM+ component using Enterprise
Services. You can then set up the component to automatically roll back the
entire transaction when there is an error. You also have manual control.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
************************************************
Think Outside the Box!
************************************************
Sonal said:
Hello, I've got a problem. I need make a transaction with two distincts
databases. The two database are SQL-SERVER. Please suggest me the best way
to do it.