Transaction is not allowed to commit inside of a user defined routine, trigger or aggregate because the transaction is not started in that CLR level. Change application logic to enforce strict transaction nesting.
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 ...
Transactional file system resource manager '%1!s!' failed to recover. For more information, see the accompanying error message, ...
Transactional replication/Change Data Capture cannot proceed because Transactional File System Resource Manager at '%1!s!' ...
Translations of cube objects can only be deployed to a server running Microsoft SQL Server Enterprise Edition or Developer ...