Howdy! I'm working with several point feature classes (300k+ records).
Sometimes I have to join these to each other, or other items of equal size. Then I'll need to select some sub-set of the data based on one or another attribute. I have frequently been experiencing Pro getting hung-up on these processes. If it involves a JOIN, sometimes I'll try to export to a Table or Feature Class, to try and get at the data from a more solidified state, but I'm generally experiencing WAY more issues with the software than I've ever had. I'll try and stop a process that's been stuck at 4% for five-ten minutes and ultimately have to Alt-Ctrl-Del my way back to a workable situation.
It's weird!
Happy to provide more context if necessary. Looking for any thoughts at all.
Thanks!
is your data sitting on a network or local?
What version of Pro are you using?
pro 3.3.1
data is local to machine. a gdb that's just a lil' folder on the C: drive!
i had previously thought things that were still connected to services and/or tucked into a folder that gets backed up to one drive was the problem, so I made things local.
hmmm have you tried repairing Pro?
Also, nowadays SSDs and new generations intel CPUs and adequate speed GDDR4 or 5 RAMs are very fast with such tasks, so the specs could be an issue too.
But being stuck at 4% might be a software issue rather than a hardware issue.
btw have you tried the Join Field tool instead of Add Join? I find the Join Field tool more smoother than Add Join
Repairing Pro? This is a new concept to me! I'm not sure what you mean.
i'll look more closely at the specs of the machine - it's usually pretty good at kerchunking through piles of stuff. that's why these isolated incidents are a big question mark for me.
I was messing around a bit with Join Field, but I hadn't committed to switching. Also Append (though slightly different uses) It's nice to know a table can be changed without making a new feature/shp/etc.
Also only found out about it after several bouts of weirdness. I'll try to see how I can implement it some more!
One thing that generally works well is a clean uninstall and clean install of ArcGIS PRo to completely remove any bouts of weirdness that the application is experiencing. You can learn more about it here - How To: Perform a Clean Uninstall and Reinstall of ArcGIS Pro (esri.com)
Thanks for the suggestion.
Do you have any 3rd party applications installed for ArcGIS Pro?
I do not.