10014: Slow join access may affect layer's draw time
You are using a joined field in a layer that may affect the drawing performance. The name of the field or fields and a description of the potential issue are provided.
Solutions
Do one of the following:
Review the drawing metrics for this layer. If you are sharing the layer, review the data access metrics for the service.
Add the attribute column directly to your feature class and modify your map and layer properties to use this new field.
Tune your layer and database implementation to ensure you can gain the best drawing performance. Many of the tips below provide guidance and best practices for how to improve drawing performance when using join fields.
Additional information
Most database design guidelines promote organizing the database into multiple tables—each focused on a specific set of columns—instead of one large table containing all the necessary fields. Having multiple tables prevents duplicating information in the database because you store the information only once in one table. When you need information that isn't in the current table, you can link the two tables together.
Learn more about joins and relates.
Joining tables to a feature class is typically done to append the fields of the table to those of the feature class table through an attribute or field common to both tables. This provides efficient storage but can have performance implications.
Tips
The following are some tips that can help improve performance in a dynamic map display.
For best performance, use an enterprise geodatabase. In cases with simultaneous users, enterprise geodatabases are faster. Since enterprise geodatabases are DBMS based, they scale better than file geodatabases in situations with a large number of users (hundreds of users or more).
For the best performance, keep your feature class table and the joined attribute table in one common geodatabase. If you cannot do this, performance will degrade. The following table summarizes potential join performance implications:
Base feature class Join table Use base table columns using inner join (select matching rows) Use join table columns using inner join (select matching rows) Use join table columns using outer join (select all records) Personal geodatabase Any DBMS including personal geodatabase Very slow Very slow Very slow File geodatabase File geodatabase Fast Fast Fast File geodatabase Enterprise geodatabase Slow Slow Slow Enterprise geodatabase File geodatabase Fast Fast Fast Enterprise geodatabase Enterprise geodatabase Fast Fast Slow Enterprise geodatabase Across to another DBMS Slow Slow Slow Create attribute indexes on your joined fields in both the feature class table and the join table.