我问自己是否可以检查ADO.NET中是否可以回滚当前事务。
msdn建议采用以下实现:
private static void ExecuteSqlTransaction(string connectionString)
{
using (SqlConnection connection = new SqlConnection(connectionString))
{
connection.Open();
SqlCommand command = connection.CreateCommand();
SqlTransaction transaction;
// Start a local transaction.
transaction = connection.BeginTransaction("SampleTransaction");
// Must assign both transaction object and connection
// to Command object for a pending local transaction
command.Connection = connection;
command.Transaction = transaction;
try
{
command.CommandText =
"Insert into Region (RegionID, RegionDescription) VALUES (100, 'Description')";
command.ExecuteNonQuery();
command.CommandText =
"Insert into Region (RegionID, RegionDescription) VALUES (101, 'Description')";
command.ExecuteNonQuery();
// Attempt to commit the transaction.
transaction.Commit();
Console.WriteLine("Both records are written to database.");
}
catch (Exception ex)
{
Console.WriteLine("Commit Exception Type: {0}", ex.GetType());
Console.WriteLine(" Message: {0}", ex.Message);
// Attempt to roll back the transaction.
try
{
transaction.Rollback();
}
catch (Exception ex2)
{
// This catch block will handle any errors that may have occurred
// on the server that would cause the rollback to fail, such as
// a closed connection.
Console.WriteLine("Rollback Exception Type: {0}", ex2.GetType());
Console.WriteLine(" Message: {0}", ex2.Message);
}
}
}
}
此外还有注释: 回滚事务时应始终使用Try / Catch异常处理。如果连接终止或者事务已在服务器上回滚,则Rollback会生成InvalidOperationException。
但我真的不相信try / catch是推荐的解决方案来检查是否可以回滚。
我知道在SQL Server实现中,如果事务是“僵尸”,则SQLTransaction对象在Connection属性上返回null。
但这是特定于实现的,它只适用于SQL Server。
是否有一种与数据库无关的方法来检测事务是否可以回滚?
TIA 马丁
答案 0 :(得分:1)
很多这种复杂性是通过在“using”语句中使用TransactionScope对象来处理的 - 在MSDN上查看它。需要注意的是,TransactionScope会在认为必要时自动“向上扩展”以使用分布式事务 - 有时这是可取的,有时则不是,所以如果要嵌套TransactionScopes,请小心。
答案 1 :(得分:0)
问题是在非SQL 2005中,transactioncope被提升为分布式事务,这是一个相当大的开销。