New answers tagged performance
This kind of operation uses a lot of work memory as I recall, so you want to make sure you are not at default settings for this which is pretty low; Try something like SET work_mem=50000; Then run your query You might want to play around with that workmem setting You'll also want to dump that into a table -- not output to screen. I assume you know that ...
Orion, I just noticed you mentioned in your response to msi_g that even after installing 64-bit Background Geoprocessing that your tool is still running in the foreground. By default, all models and script tools run in the foreground, which means by default they all run in a 32-bit environment. Have you unchecked the "Always run in foreground" checkbox on ...
Make sure you have the script tool set to run in-process. http://resources.arcgis.com/en/help/main/10.2/index.html#//00150000000r000000
Some of ArcSDE operations are pretty heavy and it is mentioned in the documentation. ESRI is improving it. Check out cursors for example (classical vs arcpy.da). One big con I can think right off the bat is that how you manage mutual exclusion and load balancing on your connection(s). Also, you may run into transactional issues, locks, etc. Note that ...
Top 50 recent answers are included