D
David Wimbush
I've been looking into adding transaction capabilities into my object
model framework. I always understood that, with SQL Server, a
transaction could only cover one database, regardless of whether the
transaction was done in a stored procedure or ADO ('classic ADO' or
ADO.Net). But when I started reading in detail it got vague. For
example, people were talking about data _sources_ instead of databases.
So I did some testing and I can do a transaction in either SQL or ADO
that successfully commits or rolls back updates to two databases. I'm
using a single SQL Server 2000 Standard Edition with multiple databases
on it and .Net 1.1.
Before I get carried away, can anybody tell me the facts or point me to
some definitive information about this, please? Thanks.
model framework. I always understood that, with SQL Server, a
transaction could only cover one database, regardless of whether the
transaction was done in a stored procedure or ADO ('classic ADO' or
ADO.Net). But when I started reading in detail it got vague. For
example, people were talking about data _sources_ instead of databases.
So I did some testing and I can do a transaction in either SQL or ADO
that successfully commits or rolls back updates to two databases. I'm
using a single SQL Server 2000 Standard Edition with multiple databases
on it and .Net 1.1.
Before I get carried away, can anybody tell me the facts or point me to
some definitive information about this, please? Thanks.