Snapshot isolation or read committed snapshot is not available in database '%1!s!' because SQL Server was started with one or more undocumented trace flags that prevent enabling database for versioning. Transaction started with snapshot isolation will fail and a query running under read committed snapshot will succeed but will resort back to lock based read committed.
Slovenian, case-sensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order ...
Snapshot can not process article '%1!s!' in publication '%2!s!', the clustered index on indexed view '%3!s!' may have been ...
Snapshot failed to process publication '%1!s!'. Possibly due to active schema change activity or new articles being added. ...
Snapshot isolation level is not supported for distributed transaction. Use another isolation level or do not use distributed ...
Snapshot isolation or read committed snapshot is not available in database '%1!s!' because SQL Server was started with one ...
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 ...