112006;Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = {0}, current count = {1}.
Transaction cannot be committed because database with name='%{db_name/}', Id='%{db_id/}' is disabled for scoped connections. ...
Transaction cannot be specified when a retained connection is used. This error occurs when Retain is set to TRUE on the connection ...
Transaction Coordination Manager is active with %1!s! as the starting AGE. This is an informational message only. No user ...
Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = %1!s!, current ...
Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = {0}, 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 ...