UPDATED:
I’m happy to share that this bug has been fixed in the latest version of 2.4! When ESRI was able to replicate the issue on their end, they did log it and resolved it and said that in 2.4 it would be live. Using ‘Select By Location’ against parcels that are both in our (DRP) SQL Server database and the Enterprise Repository, and in both cases it took a few seconds – like ArcMap did. Although it can be time consuming working with ESRI Tech Support, it is worthwhile to get issues like this fixed…especially with Pro when things aren’t quite up to snuff.
Greetings,
Those of you who are using Pro may have noticed a significant decrease in performance when performing certain Geoprocessing tasks compared to ArcMap. I had opened a ticket last month with ESRI Premium tech support, and used the ‘Select By Location’ tool as an example in that case. The simple selection I was doing was selecting the parcels on the eGIS Repository (and our SDE copy as well) with one district polygon – ultimately selecting a subset of about 200 parcels. In ArcMap this operation takes about 1 – 2 seconds, but in Pro it took over 8 minutes on my end. Thankfully ESRI could reproduce the error (faster than 8 minutes, but still unacceptable) and the results are below. They have logged it as a bug and will send it on to development. The issue seems to be working with any remote database….Pro is very chatty and slow in that regard. I will let you all know when I hear any resolution on this. I’m sure this will be a topic of discussion in the coming year when we start our ArcGIS Pro Working Group.
From ESRI….
Hello Dan,
Thanks for your patience! I’ve went ahead and logged the following bug:
[BUG-000119042: Select by Location performance to an enterprise geodatabase is significantly worse from ArcGIS Pro than ArcGIS for Desktop.]
Also, just for your reference, here were my testing results. I’d like to note that PostgreSQL seems to work a bit better than SQL Server and Oracle, in case that’s a better option for you for performance.
File Geodatabase:
– ArcMap 10.6.1: Less than a second.
– ArcGIS Pro 2.2.4: Less than a second.
– ArcGIS Pro 2.3 Beta: Less than a second.
SQL Server:
– ArcMap 10.6.1: Less than a second.
– ArcGIS Pro 2.2.4: 3 minutes, 45 seconds.
– ArcGIS Pro 2.3 Beta: 3 minutes, 9 seconds.
Oracle:
– ArcMap 10.6.1: Less than two seconds.
– ArcGIS Pro 2.2.4: 3 minutes, 57 seconds.
– ArcGIS Pro 2.3 Beta: 3 minutes, 25 seconds.
PostgreSQL:
– ArcMap 10.6.1: About 3 seconds.
– ArcGIS Pro 2.2.4: 1 minute, 43 seconds.
– ArcGIS Pro 2.3 Beta: 1 minute, 3 seconds.
At this point, Development will have to review the bug and get back to us. There won’t be much more I can do at this point. Let me know if you have any further questions or if you’re all set to close the case?