We discussed a few best practices earlier for map service MXDs; now, let's examine some more settings and configurations that can affect map service performance:
- Joins and relates. This is a big one; many times, enterprise data is kept in systems outside of GIS. It's tempting to add that data and join or relate it based on a primary field. While this may be fine for desktop applications and daily use, it doesn't scale well and tends to perform poorly when used on larger datasets. In these cases, it is often best to develop a script to be run as a scheduled task that will join the enterprise data onto the GIS data which can then be consumed by your web services. For more information, search the ArcGIS Enterprise online documentation ...