The session timeout value was exceeded while waiting for a response from the other availability replica in the session. That replica or the network might be down, or the command might be misconfigured. If the partner is running and visible over the network, retry the command using correctly configured partner-connection parameters.
The session has been terminated because it has acquired too many locks. Try reading or modifying fewer rows in a single transaction. ...
The session has been terminated because of excessive TEMPDB usage. Try modifying your query to reduce temporary table space ...
The session has been terminated because of excessive transaction log space usage. Try modifying fewer rows in a single transaction. ...
The session keys for this conversation could not be created or accessed. The database master key is required for this operation. ...
The session timeout value was exceeded while waiting for a response from the other availability replica in the session. That ...
The session was cancelled because it exceeded a timeout setting (session orphaned timeout or session idle timeout) or it ...
The session was enlisted in an active user transaction while trying to bind to a new transaction. The session has defected ...
The session with SPID %1!s! was found to be invalid during termination, possibly because of corruption in the session structure. ...
The set of tuning options (-fa, -fp, -fk) that you have supplied is invalid. This combination is not supported for indexed ...