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; } } }

Join Field - WARNING 000970 Slow performance

PeterMerx1

Hi,

I'm joining a standalone table to a shape. When joining i get the WARNING 000970 about my join field. When the join is ready I want to work with the shapefile but it is extremely slow. After Feature class to Feature class it is much better but this tool takes a long time. If i run the Add Attribute Index tool on the join field i don't get any enhancement in performance and I still get the warning 000970 although I just ran the Add Attribute Index on the field. What can I do to improve performance on the shapefile I'm working with?

Trouver plus de publications taguées avec

Accepted answers

All comments

DanPatterson_Retired

you failed to indicate the size of the file you are trying to join. It may just be quite large. What type of fields are involved in the joins? Joining a geodatabase table to a geodatabase featureclass is probably as fast as you are going to get it they are both indexed on the join field.

JayantaPoddar

You could upvote the idea Improve performance of the Join Field tool

Maybe the Standalone Python script would be faster. Join Field—Data Management toolbox | ArcGIS Desktop

Working with FGDB Feature classes is more preferable than shapefiles.

PeterMerx1

The thing is, i get the WARNING 000970 before joining! And if i run the Add Attribute Index tool, i get the warning again. After I run the feature class to feature class tool the performance of the shapefile is greatly enhanced, for example when selecting specific symbology.
The file is 100.000 records....

DanPatterson_Retired

You keep mentioning shapefile... is there a reason that you can't copy the shapefile to a featureclass in a geodatabase and do everything in a geodatabase? If you then need a shapefile with the data permanently joined after, you can do it at the end of the workflow, assuming you don't hit the 2 Gb file size limit.

PeterMerx1

I'm sorry you're right...it's a feature class in a gdb (I add it from the .gdb to from Catalog). I'm joining it to a standalonetable.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

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