0

在 T-Sql 中，rollback transaction回滚除指定保存点名称之外的所有事务。要仅回滚部分修改，我们使用rollback transaction @save_point_name. 这是一个save transaction @save_point_name必须早先说明的。如果引用的保存点已经回滚（从事务日志中删除），则会引发错误。同样，如果没有活动事务，则begin transaction @transaction_name需要声明 a，并且可以以相同的方式回滚。这可以快速发现错误或使用try...catch机制。

与 不同rollback，完全commit transaction @transaction_name忽略它的@transaction_name部分，只执行提交，减少@@trancount或结束事务。因此，无法知道或指定哪个（嵌套）事务，或者就此而言 - 一个保存点，正在（伪）提交。我知道事务一开始并不意味着嵌套，因此存在保存点。

一种典型的方法是，在每个过程中，检查@@trancount以确定是创建保存点还是开始新事务。然后，确认确定，检查事务状态并相应地提交或回滚（或什么都不做）。

这种检查是很多样板文件，尤其是当您有很多程序调用（多个）程序时，所有这些程序都只会在出现问题时回滚自己的操作。所以我的尝试是抽象事务，以便人们可以简单地编写这样的东西。

create procedure RollBackOnlyMyActions
as
declare @SavePointName nvarchar(32) = N'RollBackToHere';
begin try
    exec CreateSavePoint @SavePointName;    

    --do stuff

    --call other procedures that may roll back only its actions

    --do other stuff

    exec CommitSavePoint @SavePointName;
end try
begin catch
    exec RollBackSavePoint @SavePointName;
end catch

在哪里（让我打印出来）

create procedure dbo.CreateSavePoint
    @SavePointName nvarchar(32)
as
declare @Msg nvarchar(255);
print N'Preparing to create save point ['+@SavePointName+N'].';
print N'Checking not in an uncommitable transaction.';
if xact_state() != -1 
begin 
    print N'Not in an uncommitable transaction. Checking for transaction existence.';
    if @@TranCount = 0
    begin
        print N'No active transaction. Starting a new one.';
        begin transaction @SavePointName;
    end
    else
    begin
        print N'In active transaction. Saving transaction point.';
        save transaction @SavePointName;
    end
end
else
begin
    print N'In an uncommitable transaction. No use saving. Throwing exeption.';
    set @Msg = N'Uncommitable transaction.';
    throw 50000,@Msg,1;
end
go

create procedure dbo.CommitSavePoint
    @SavePointName nvarchar(32)
as
declare @Msg nvarchar(255);
print N'Preparing to commit save point ['+@SavePointName+N'].';
print N'Checking not in an uncommitable transaction.';
if xact_state() != -1
begin
    print N'Not in an uncommitable transaction. Checking transaction count.';
    if @@trancount > 1
    begin
        print N'In nested transaction of '+convert(nvarchar(255),@@trancount)+N'. Committing once.';
    end
    else if @@trancount = 1
    begin
        print N'In outter transaction. Committing.';        
    end
    else
    begin
        print N'No active transaction. Throw exception.';
        set @Msg = N'No transaction to commit.';
        throw 50000,@Msg,1;
    end
    commit transaction;
end
else
begin
    print N'In an uncommitable transaction. Cannot commit. Throwing exeption.';
    set @Msg = N'Uncommitable transaction.';
    throw 50000,@Msg,1;
end
go

create procedure dbo.RollbackSavePoint
    @SavePointName nvarchar(32)
as
declare @Msg nvarchar(255);
print N'Prepare to rollback savepoint ['+@SavePointName+N']';
print N'Checking not in an uncommitable transaction.';
if xact_state() != -1 
begin 
    print N'Not in an uncommitable transaction. Trying rollback';
    begin try
        rollback transaction @SavePointName;
    end try
    begin catch
        print N'Something went wrong. Rethrowing exception.';
        throw;
    end catch
end
else
begin
    print N'In an uncommitable transaction. No use rolling back. Throwing exeption.';
    set @Msg = N'Uncommitable transaction.';
    throw 50000,@Msg,1;
end
go

好吧，这没有用。当我得到一个

Msg 266, Level 16, State 2, Procedure CreateSavePoint, Line 0
Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1.

在第一次调用 CreateSavePoint 之后。也就是说，似乎 sql server 不喜欢跨多个过程管理事务。

所以。是否有任何解决方法，例如抑制此错误的方法？或者我在这里错过了一个重要的概念？

4

1 回答 1

0

回滚问题可以通过使用“自动回滚”（简单）并抑制错误 266 的 SET XACT_ABORT ON 来解决。

于 2014-07-22T19:36:56.563 回答