ArcGIS Server 10.7.1: What is the best practice to improve the performance of a versioned geodatabase feature class?
I couldn’t figure out the best practice to improve the performance of a versioned geodatabase feature class.
Jamal - a lot of these workflows can be automated using a Python script associated with Task Scheduler in Windows. I show my Versioning students this link - of course it's Python27 so you'd have to run the Analyze Tools for Pro GP tool to ensure it will work in AGP as the Python release is much different in AGP.
Thanks Robert.
Function wise:
Do compress and analyze tools improve view and edit performance?
Does rebuild indexes improve query performance?
Jamal - function wise deserves an explanation:
Hope this helps!
Thanks for the very useful input.
Is it correct to conclude this:
Compress tools helps improve the performance in viewing, display, and query
Rebuild indexes tool: helps improve the performance in querying
Analyze tool: helps improve the performance in querying
Yes, I'd say that's correct to conclude.
Your original question was about improving the performance of a versioned feature class.
I would say that viewing, displaying and querying are ALL affected by the perfomance of the underlying SQL queries against the Enterprise Geodatabase. As such, reconcile, compress and index/statistics management will all help keep SQL queries optimized.
The display performance within a desktop client directly connecting to the geodatabase or a web services client (Browser or Pro or Mobile) accessing traditional Map/Feature Service - will also be affected by good configuration of the original resource that is published (Map Document or Pro Project) to ensure you are not drawing the feature at inappropriate scales or trying to return too many vertices, or using complex labelling or symbolization. These are all different performance improvements that may be required. You can use tools such as MXDPerfstat or PerfQAnalyzer to provide some guidance on these.