The DTC allows for transactions to straddle multiple databases. It works out the transaction and allows one to write to one database and then roll back that change when failing to write to a second database. It going to allow one to slurp in a second connection string, I believe. Putting...
enlist=false;
...in a connection string will keep transactions restrained to a single database so that basically after a write to one database and a failed write to another the write to the first database is not undone. There is, without this, some after the fact auditing across the two databases to make sure things are shipshape. None of this is just going to work out the box. The databases have to have permissions opened up.
No comments:
Post a Comment