前段时间，我在ArcMap的外部COTS系统中打开了一个WORKORDER表。这个表格有200多列。尽管ArcMap只有几千行，但我很惊讶它在ArcMap中的运行速度有多慢。我记得当将列减少到几个列时，性能会更好。在视图层或查询层中。因此，可以考虑提前减少列的数量。(定义查询不会省略列;只有适当的查询，如视图或查询层可以省略列。)当属性中的字段被禁用时，不要选择*。另外，视图可以使用适当的连接。然而，我想知道ArcGIS中的“连接”是否使用子查询，而不是正确的连接; proper joins are often faster. And then there are attribute indexes. I don’t know if indexes would improve performance in SELECT queries with WHERE clauses or not. But I think indexes would help with other things like JOINs. See: SQL Performance Explained You could also make sure that your WHERE clauses are structured to be as performant as possible. For example: LIKE is slow. =, IN, EXISTS are faster. If a column is wrapped in a function such as UPPER(), then an index can’t be used when querying that column. Subqueries are slow. In newer versions of ArcGIS Pro, you can see what queries are being sent to the database by looking at the Diagnostic Monitor. That might help you troubleshoot slow tables. It would be nice if we could control how a table or layer gets cached in ArcGIS Desktop. For example, if a table is slow in ArcGIS Pro, tell Pro to cache it in RAM and only refresh it every n minutes. And refresh it in the background; don’t make me wait. That might be better than refreshing the table after every click the user makes in the map or attribute table. Idea: Control caching settings for better performance in event layers & query layers You could also look into compressing versioned data, refreshing database statistics, spatial indexes, and Geoprocessing, Resolution, Tolerance, and Hair. Also, it’s occurred to me that organizations might see performance improvements after upgrading their enterprise geodatabase to a newer database version. That might “refresh” the data as a last resort. But I don’t have expertise in any of those things. You could look into Indexed Views in SQL Server. https://stackoverflow.com/questions/3986366/how-to-create-materialized-views-in-sql-server. Or other ways of pre-computing queries, like exporting a subset of a table on a schedule. And use that exported table in ArcMap instead, which might be faster. Or even a simple data cleanup exercise might help. Delete old and unneeded columns. Edit: Scale ranges for layers and labels might help too. I.e., make layers or labels only visible at certain scales -- some layers/labels might not be needed when zoomed out or zoomed in. For polygon and polyline layers, consider removing superfluous vertices via "Simplify" geoprocessing tools, etc.. A few posts related to automation: What levels of the ArcGIS Enterprise stack support scheduled jobs? Options for computing fields Precompute field on a schedule Rebrand and expand Notebook Server as "ArcGIS Automation Server" Practical GIS automation for non-IT users Scheduled reports in ArcGIS Enterprise? (emailed; condition-based) Automation - GIS Strategy Scheduled/emailed reports using ArcGIS Notebook Server? Scheduled automation for everyday ArcGIS Pro users I haven't actually implemented that stuff. I was just looking for clean ArcGIS automation solutions as a non-IT person. I haven't really found what I'm looking for yet.