AnsweredAssumed Answered

READ_COMMITTED_SNAPSHOT=ON is Mandatory in an ArcGIS 10.5 Server environment

Question asked by micsbjc on Nov 29, 2017
Latest reply on Feb 21, 2018 by 96213@charlottenc.gov_charlotte

We have a mixed ArcGIS environment (10.2.1 and 10.5) connecting to a 10.2.1 Enterprise geodatabase SQL Server .2016.

 

https://support.esri.com/en/technical-article/000013039 states (in part)

"Using ArcGIS 10.4 with SQL Server databases or 10.3.1 or earlier release geodatabases, requires manually setting READ_COMMITTED_SNAPSHOT to ON in the database"

 

Does this imply that you MUST set these values, or you CAN set these values.

 

This is important to us as the ESRI code in the Map Services in our 10.2 ArcGIS environment start a transaction at startup and retain this until shutdown (24 hours later). With READ_COMMITTED_SNAPSHOT turned on we will have to make TempDB big enough to retain 24 hours of database updates (or recycle the mapservices on a more regular basis).

 

On the other side, if the answer is 'CAN set these values' then in our 10.5 ArcGIS Server we have lost whatever protection that the longrunning open transaction provide in 10.2 and we have not gained any protection that was offered by the READ_COMMITTED_SNAPSHOT change.

 

Can anyone confirm one way or the other?

 

EDIT: I have been advised by ESRI support that it is mandatory. I also found another link  http://desktop.arcgis.com/en/arcmap/latest/manage-data/geodatabases/concurrency-and-locking.htm that was more definitive

  • Beginning with ArcGIS 10.4, geodatabases in SQL Server must have the SQL Server database options READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION set to ON. When you edit a geodatabase in SQL Server in a nonversioned edit session, ArcGIS uses the READ COMMITTED isolation level for transactions.

Outcomes