10.4 Parcel Fabric-Prozesse haben sich erheblich verlangsamt

Question

<\/HEAD>Hallo zusammen,<\/P> <\/P> Ich habe gerade auf 10.4 aktualisiert und festgestellt, dass verschiedene Parcel Fabric-Tools\/Dialoge im direkten Vergleich zu einer 10.3.1-Maschine sehr lange zum Laden und Verarbeiten benötigen. Unser Fabric befindet sich in SQL Server 2014. Ich habe die gespeicherten Prozeduren in der Datenbank aktualisiert, und die Leistungsprobleme bestehen weiterhin. <\/P> <\/P> Der Duplicate-Dialog benötigt etwa 45 Sekunden, um angezeigt zu werden, und weitere 55 Sekunden, um ein einzelnes Parcel zu duplizieren. Der Parcel Division-Dialog wird schnell angezeigt, aber der Vorgang, ein einzelnes Parcel in 2 Teile zu teilen, dauert etwa eine Minute.<\/P> <\/P> Gibt es Tipps für die Migration, die helfen könnten?<\/P> <\/P> Danke, Mike<\/P><\/BODY><\/HTML>

TimHodson · Answer

Mike,

Thanks again for reporting this, and for sharing your data via tech support. I'm responding again here to share findings with other customers who may have experienced similar issues with SQLServer. The delay was caused by a combination of 2 things: some changes made to the cursor model for 10.4 on SQLServer, and the Uncommitted records (Status=0) in the jobs table. The latter records are accumulated when editing directly against default, instead of in a version. We recommend editing in a version since posting the version will automatically commit the job for you (Status=1). If there is a need to edit directly on default, then after the edit we'd recommend manually committing the job afterwards.

To clear out the jobs table, you can un-register the fabric as versioned, then use the Delete Fabric Records add-in 's Truncate command to "Drop all fabric jobs"

-Tim

MichaelSnook · Answer

Tim,

I am able to run queries to get these properties and they are both on (1) for 'is_read_committed_snapshot_on' and 'snapshot_isolation_state' properties.

Mike

TimHodson · Answer

Hi Mike,

There's a section in the What's New at 10.4 doc, that may help to solve your problem:

http://desktop.arcgis.com/en/arcmap/latest/get-started/introduction/whats-new-in-arcgis.htm#GUID-BFAB27B8-04AA-4C21-90D0-C63B7A7A4E59

* Beginning with ArcGIS 10.4, geodatabases in SQL Server
     require the SQL Server database options READ_COMMITTED_SNAPSHOT and
     ALLOW_SNAPSHOT_ISOLATION be set to ON. When you upgrade your geodatabase
     in SQL Server, the Upgrade Geodatabase tool sets these in the database.
     When you create a geodatabase in SQL Server using the Create Enterprise
     Geodatabase tool, the tool sets these options in the database. If you use
     the Enable Enterprise Geodatabase tool to create a geodatabase, you must
     either set these options to ON in the database before you run the tool, or
     grant the geodatabase administrator the permission to ALTER the database.
     If the geodatabase administrator has ALTER database permission, the Enable
     Enterprise Geodatabase sets READ_COMMITTED_SNAPSHOT and
     ALLOW_SNAPSHOT_ISOLATION to ON in the database.

To use ArcGIS 10.4 with SQL Server databases or 10.3.1 or
earlier release geodatabases, you must manually set on READ_COMMITTED_SNAPSHOT
in the database.