Snapshot isolation transaction failed in database '%1!s!' because the object accessed by the statement has been modified by a DDL statement in another concurrent transaction since the start of this transaction. It is disallowed because the metadata is not versioned. A concurrent update to metadata can lead to inconsistency if mixed with snapshot isolation.
Snapshot isolation transaction aborted due to update conflict. You cannot use snapshot isolation to access table '%1!s!' ...
Snapshot isolation transaction failed accessing database '%1!s!' because snapshot isolation is not allowed in this database. ...
Snapshot isolation transaction failed in database '%1!s!' because the database did not allow snapshot isolation when the ...
Snapshot isolation transaction failed in database '%1!s!' because the database was not recovered when the current transaction ...
Snapshot isolation transaction failed in database '%1!s!' because the object accessed by the statement has been modified ...
Snapshot isolation transaction failed in database '%1!s!' because the recovery was skipped for this database. You must recover ...
Snapshot isolation transaction failed to start in database '%1!s!' because the ALTER DATABASE command that disallows snapshot ...
Snapshot isolation transaction failed to start in database '%1!s!' because the ALTER DATABASE command which enables snapshot ...
Snapshot publications cannot use the option to initialize a subscription from a backup. This option is only supported for ...