Transaction count has been changed from %1!s! to %2!s! inside of user defined routine, trigger or aggregate "%3!s!". This is not allowed and user transaction will be rolled back. Change application logic to enforce strict transaction nesting.
Transaction (Process ID %1!s!) was deadlocked on %2!s! resources with another process and has been chosen as the deadlock ...
Transaction aborted when accessing versioned row in table '%1!s!' in database '%2!s!'. Requested versioned row was not found. ...
Transaction cannot be specified when a retained connection is used. This error occurs when Retain is set to TRUE on the connection ...
Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = %1!s!, current ...
Transaction count has been changed from %1!s! to %2!s! inside of user defined routine, trigger or aggregate "%3!s!". This ...
Transaction failed because this DDL statement is not allowed inside a snapshot isolation transaction. Since metadata is not ...
Transaction failed in database '%1!s!' because the statement was run under snapshot isolation but the transaction did not ...
Transaction is not allowed to commit inside of a user defined routine, trigger or aggregate because the transaction is not ...
Transaction is rolled back when accessing version store. It was earlier marked as victim when the version store was shrunk ...