如何设计dt和dd，以便它们在同一行？(How to style dt and dd so they are on the same line?)

 这是我们的模板（删除错误记录） 
 
 这是设计来处理 
 
 
 
 Paul Randal的文章“没有像SQL Server中的嵌套事务那样的事情” 
 
 
 错误266 
 
 
 触发器回滚 
 
 
 说明： 
 
 
 
 所有TXN开始和提交/回滚必须配对，以便@@TRANCOUNT在进入和退出时是相同的 
 
 
 @@TRANCOUNT错配导致错误266因为 
 
  
 
   
 BEGIN TRAN增量@@TRANCOUNT 
 
   
 COMMIT递减@@TRANCOUNT 
 
   
 ROLLBACK返回@@TRANCOUNT为零 
 
  
 
 
 您不能在当前范围内递减@@TRANCOUNT 
 这就是你认为的“内部交易” 
 
 
 SET XACT_ABORT ON抑制由不匹配的@@TRANCOUNT引起的错误266 
 并且还处理dba.se上这样的“SQL Server事务超时”问题 
 
 
 这允许客户端TXN（如LINQ）单个存储过程可能是分布式或XA事务的一部分，或者仅仅是在客户端代码中启动（例如.net TransactionScope） 
 
 
 用法： 
 
 
 
 每个存储的proc必须符合相同的模板 
 
 
 概要 
 
 
 
 所以不要创建比你需要的更多的TXN 
 
 
 代码 
 
CREATE PROCEDURE [Name]
AS
SET XACT_ABORT, NOCOUNT ON

DECLARE @starttrancount int

BEGIN TRY
    SELECT @starttrancount = @@TRANCOUNT

    IF @starttrancount = 0
        BEGIN TRANSACTION

       [...Perform work, call nested procedures...]

    IF @starttrancount = 0 
        COMMIT TRANSACTION
END TRY
BEGIN CATCH
    IF XACT_STATE() <> 0 AND @starttrancount = 0 
        ROLLBACK TRANSACTION;
    THROW;
    --before SQL Server 2012 use 
    --RAISERROR [rethrow caught error using @ErrorNumber, @ErrorMessage, etc]
END CATCH
GO
 
 笔记： 
 
 
 
 由于SET XACT_ABORT ON ，回滚检查实际上是多余的。 然而，它让我感觉更好，看起来很奇怪，而且允许你不想要的情况 
 
 
 Remus Rusanu有一个类似的shell ，它使用保存点。 我更喜欢原子数据库调用，不要像他们的文章一样使用部分更新 
 

This is our template (error logging removed)
 
This is designed to handle
 
 
 
Paul Randal's article "No such thing as a nested transaction in SQL Server"
 
 
Error 266
 
 
Trigger Rollbacks
 
 
Explanations:
 
 
 
all TXN begin and commit/rollbacks must be paired so that @@TRANCOUNT is the same on entry and exit
 
 
mismatches of @@TRANCOUNT cause error 266 because
 
  
 
   
BEGIN TRAN increments @@TRANCOUNT
 
   
COMMIT decrements @@TRANCOUNT
 
   
ROLLBACK returns @@TRANCOUNT to zero
 
  
 
 
You can not decrement @@TRANCOUNT for the current scope
 This is what you'd think is the "inner transaction"
 
 
SET XACT_ABORT ON suppresses error 266 caused by mismatched @@TRANCOUNT
 And also deals with issues like this "SQL Server Transaction Timeout" on dba.se
 
 
This allows for client side TXNs (like LINQ) A single stored procedure may be part of distributed or XA transaction, or simply one initiated in client code (say .net TransactionScope)
 
 
Usage:
 
 
 
Each stored proc must conform to the same template
 
 
Summary
 
 
 
So don't create more TXNs than you need
 
 
The code
 
CREATE PROCEDURE [Name]
AS
SET XACT_ABORT, NOCOUNT ON

DECLARE @starttrancount int

BEGIN TRY
    SELECT @starttrancount = @@TRANCOUNT

    IF @starttrancount = 0
        BEGIN TRANSACTION

       [...Perform work, call nested procedures...]

    IF @starttrancount = 0 
        COMMIT TRANSACTION
END TRY
BEGIN CATCH
    IF XACT_STATE() <> 0 AND @starttrancount = 0 
        ROLLBACK TRANSACTION;
    THROW;
    --before SQL Server 2012 use 
    --RAISERROR [rethrow caught error using @ErrorNumber, @ErrorMessage, etc]
END CATCH
GO
 
Notes:
 
 
 
The rollback check is actually redundant because of SET XACT_ABORT ON. However, it makes me feel better, looks odd without, and allows for situations where you don't want it on
 
 
Remus Rusanu has a similar shell that uses save points. I prefer an atomic DB call and don't use partial updates like their article