HOW TO
Row versioning-based isolation levels improve read concurrency by eliminating locks for read operations. Microsoft SQL Server 2008 R2 and later releases introduce two transaction isolation levels that use row versioning:
Beginning with ArcGIS 10.4, read-committed is the default isolation level for transactions. There are also times when networks in the geodatabase use snapshot isolation.
As a result the SQL Server database options READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION must bet set ON for all 10.4 geodatabases.
The READ_COMMITTED_SNAPSHOT database option determines the behavior of the default read committed isolation level when snapshot isolation is enabled in a database. If you do not explicitly specify READ_COMMITTED_SNAPSHOT ON, read committed isolation is applied to all implicit transactions and ArcGIS 10.4 will encounter locking issues that will affect performance and scalability.
ALTER DATABASE MyDatabase SET READ_COMMITTED_SNAPSHOT ON
The ALLOW_SNAPSHOT_ISOLATION database option enables the database to use snapshot isolation. If you do not explicitly specify ALLOW_SNAPSHOT_ISOLATION ON, ArcGIS 10.4 could encounter issues while working with network data.
ALTER DATABASE MyDatabase SET ALLOW_SNAPSHOT_ISOLATION ON
Get help from ArcGIS experts
Download the Esri Support App