SDE Performance Degradation Using Topology with Large Datasets

2933
15
05-16-2019 01:34 PM
Status: Open
Labels (1)
CoryBowlin
New Contributor III

Currently ESRI'S SDE geodatabase has performance degradation issues when adding, deleting, or making attribution changes on features when the SDE utilizes a Topology on a large dataset (example: 30,000 polygons representing land parcels and five rules involving three Feature Classes).   According to ESRI, this slowness should be expected on SQL Server, Oracle, and PostgreSQL when a topology feature class is used. The database is performing checks on "dirty areas" when edits are made causing the process to be slow.

 

I suggest making a modification to the enterprise geodatabase design to handle edits in a way that does not degrade speed while using toplogies or add the Disable Network Topology functionality to non-network topologies. A enhancement request has been logged with ESRI for such a tool:  ENH-000122376    

15 Comments
CoryBowlin

Currently ESRI'S SDE geodatabase has performance degradation issues when adding, deleting, or making attribution changes on features when the SDE utilizes a Topology on a large dataset (example: 30,000 polygons representing land parcels and five rules involving three Feature Classes).   According to ESRI, this slowness should be expected on SQL Server, Oracle, and PostgreSQL when a topology feature class is used. The database is performing checks on "dirty areas" when edits are made causing the process to be slow.

I suggest making a modification to the enterprise geodatabase design to handle edits in a way that does not degrade speed while using toplogies or add the Disable Network Topology functionality to non-network topologies. A enhancement request has been logged with ESRI for such a tool:  ENH-000122376    

KoryKramer
KoryKramer
MichaelVolz

Cory:

Are you seeing this degradation in ArcMap or Pro?  It's unclear to me from your idea and Kory's links shows Pro help.

MichaelVolz

Cory:

Are you seeing this degradation in ArcMap or Pro?  It's unclear to me from your idea and Kory's links shows Pro help.

CoryBowlin

This slow performance occurs in Pro and in desktop 10.6, 10.6.1, and 10.7.  The issue was also reproduced by ESRI on their hardware and even with other data. 

CoryBowlin

This slow performance occurs in Pro and in desktop 10.6, 10.6.1, and 10.7.  The issue was also reproduced by ESRI on their hardware and even with other data. 

JoshMcCracken

Cory,

Would you have any suggested steps for working around this issue until the tool that you mentioned might be introduced?

JoshMcCracken

Cory,

Would you have any suggested steps for working around this issue until the tool that you mentioned might be introduced?

CoryBowlin

Temporarly turning off the topolgy rules should do it. Unfortunately with the environment that I had this sde deployed in, it would cause the sde replication to break if you modify the topolgy rules. So turning them off wasn't an option in my situation. 

Another idea I had, even with the replication, was to deploy the replication using sde binary storage type. One problem with this possibility is sde binary is deprecated in pro. I never got to test this theory but several clues led me to believe it may work. I did try other storage types that did not make a difference.