nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Delete features and Append issue

Tonyalmeida

I have a layer that is created by a python script that is used in portal and map service. It is in a SDE database and the script deletes all the features and then appends the new features that are created by the script. The issues that I am having is that the more and more I run the script it seems as the feature class/layer gets slower. For example if I try to preview the feature class in ArcCatalog it takes a long time to display the feature class, longer than it should. The same goes for the map service, this feature class in a Map Service. The a query from this map service takes a long time. What is the issue? Is there a better way to delete features and append features?

Find more posts tagged with

Accepted answers

All comments

Tonyalmeida

We do run a compression every night but I will have to look deeper into the database to see if there is an issues with the compression. I figured that if I did a delete features on the entire feature class it would delete everything, which is what I want. I have ran the delete features on the feature class and have verified in ArcCatolog that all the features were deleted.

So if it's versioned and I run the delete features, then append it doesn't delete the old records?

jskinner

@TonyAlmeida I second @Anonymous User for compressing the geodatabase. You mentioned your feature class is versioned, so each time the delete features/append occurs you are adding records to the delta tables (A & D tables). If there are 10,000 features, you are adding 10,000 new rows to the A table, and 10,000 new rows to the D table. ArcGIS queries these tables to display/query the feature class. The larger these tables are, the longer it will take to query/display.

In order to compress the geodatabase, you will want to make sure there are no locks on the feature classes. This means, you'll need to stop all ArcGIS Server services referencing data from your Enterprise Geodatabase. Here is a tool that may be helpful for you:

https://community.esri.com/t5/data-management-documents/compress-geodatabase-tool/ta-p/908944

Tonyalmeida

The feature class is Versioned and according to the help doc it can't be versioned.

JoeBorgione

Another argument for branch versioning: no compressing needed!!

Anonymous User

Are you compressing the database at all in any of your database maintenance routines? There are some caveats to this so it may/ may not be applicable to your environment/ database so check out the Usage.

compress

JoeBorgione

If your workflow does indeed call for all features to be deleted, I suggest using truncate instead.

Tonyalmeida

I am using arcpy.DeleteFeatures_management. It does appear to delete them all when I use arcpy.DeleteFeatures_management.

JoeBorgione

How are you deleting the features? Does everyone of them get deleted? If so, I suggest using truncate. It's always done a good job for me.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.