Bug
Joining a feature class to a nonspatial table takes a long time if the joining members are located on separate geodatabases.
| Bug ID Number | NIM091661 |
|---|---|
| Submitted | May 14, 2013 |
| Last Modified | April 2, 2025 |
| Applies to | ArcGIS for Desktop |
| Version found | 10.1 |
| Status | Non-Reproducible |
Additional Information
If data participating in a join resides in two separate geodatabases it will likely be slower than if all the data resides together. There may be many contributing factors such as network latency if the data is physically not co-located on the same machine. Also, ArcGIS will treat the join differently as the data is coming from two different workspaces and joins in that situation cannot be pushed down to the database for processing. However, this bug, as written, with the data provided, was not sufficient to produce a pronounced difference in join speed.Workaround
Place the nonspatial table and the feature class on the same geodatabase.Steps to Reproduce
Bug ID: NIM091661
Software:
- ArcGIS for Desktop
Get notified when the status of a bug changes
Discover more on this topic
Search for related information
Find training related to this topic
Explore ideas and give feedback
Get help from ArcGIS experts
Download the Esri Support App