Schema Operations Very Slow

[MobiusSnake]

Hi all,

I have a colleague using Pro, once any of his projects have been worked on for more than a few days, schema operations like deleting feature class, adding/dropping fields, etc., become very, very slow.  For example, dropping a field on a feature class with fewer than ten records will take 15-20 seconds.  It seems to be limited to schema changes, everything else in Pro performs as expected.

His machine has decent specs, running v3.4, and this doesn't happen to myself or others doing the same workflows.  We've tried cleaning up GP history, things like that, but the only resolution we've found is starting a fresh project.  All of the GDBs involved are on a local SSD.

Has anyone run into this before?  I'm stumped as to why it's only impacting this single machine, and not other near-identical machines performing similar tasks.

Thanks!

[RichardDaniels]

Based on your description, the first thing I would check is the geoprocessing history. Per ESRI "Geoprocessing tools add metadata about their execution in a geodatabase. The metadata includes the tool name, its location, and the parameters used when geoprocessing logging is enabled. Enterprise Geodatabases with large metadata stored can impact the performance."

GIS users, or ArcSDE administrators sometimes need to delete the geoprocessing history from a feature class or workspace metadata.

This same issue was reported in 2018 at How to remove GP History - Esri Community