We are having performance issues with feature classes joined with sql table views inside arcmap. We use this approach in arcmap as well as to publish the content as services to ArcGIS Server. The database gets constant updates so it is crucial that we maintain relationship between the feature class and sql view. There are typically 2000 to 4000 records on the joined table. The performance is very slow. We use this approach with many feature classes and tables and they show the same symptoms. Any help would be appreciated.
Can you add the following information:
ArcGIS Client used?
What is the name and version of the RDBMS you are using?
What version is the Geodatabase?
For the joined data, it is in the same database (no registered with the geodatabase) or in another completely different database?
How long is too long?
With out the above information it will be difficult for people to help.
George, thank you for your response. Here is the information.
ArcGIS client : Desktop 10.3.1
Database : SQL server 2008 R2
Geodatabase version : unknown
Feature class is on a File GDB and joined table exists on a separate standalone sql database view.
It takes few minutes for everything to load and if zoomed in or out, same amount of time.
Do you have attribute indexes created on the fields that create the join?
Based on that information, I would wonder how any join between a file geodatabase and another SQL Server database view would perform.
I will try adding indexes and see how it will work. Thank You for your help.
Thanks guys that really did work and performance is significantly better now.