The transaction executed too many insert, update, or delete statements in memory optimized tables. The transaction was terminated.
The transaction cannot be reversed. Either this transaction type cannot be reversed or a related transaction must be reversed ...
The Transaction Coordination Manager has encountered error %1!s!, state %2!s!, severity %3!s! and is shutting down. This ...
The transaction could not be committed because an error occurred while tyring to flush FILESTREAM data to disk. A file may ...
The transaction encountered an out-of-memory condition while rolling back to a savepoint, and therefore cannot be committed. ...
The transaction executed too many insert, update, or delete statements in memory optimized tables. The transaction was terminated. ...
The transaction for posting merge snapshot commands to the Publisher database had been chosen as a deadlock victim, the operation ...
The transaction has been stopped because it conflicted with the execution of a FILESTREAM close operation using the same ...
The transaction log contains a record (logop %1!s!) that is not valid. The log has been corrupted. Restore the database from ...
The transaction outcome. This will be true if the resolution was to commit the transaction or false if the resolution was ...