nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS Server 10.7.1: What is the best practice to improve the performance of a versioned geodatabase feature class?

JamalNUMAN

I couldn’t figure out the best practice to improve the performance of a versioned geodatabase feature class.

Find more posts tagged with

Accepted answers

All comments

Anonymous User

Are you working with branched or traditional versioning?

JamalNUMAN

Traditional! but what if it's branched?

Anonymous User

Hi Jamal

I think if you are going to use map/feature services, you might need to have a look at branch versioning.

Editing and Administration with Branch Versioning – It’s Showtime!

Regards,

Bing

DavidHoy

Hi Jamal,

to answer your original question

hands down the most important thing you can do to keep the performance optimized for your traditionally versioned geodatabase is to introduce a regime of reconcile, compress and rebuild statistics. (ideally as a scheduled python script)

If you dont do this, the state_lineage tree that determines the number of internal datatabase queries (between the sde_states, sde_state_lineage and the base+A&D tables that make up the versioned feature class) that are required to return the "current" value of your feature classes can become enormous, particularly if the class is being edited frequently.
I have seen sites where there was no compress happening for months and once performed, queries dropped from minutes to sub-second.

JamalNUMAN

Many thanks David for the help.

How about “rebuild indexes” tool? Has it something to do with enhancing the performance of the a versioned feature class?

Robert_LeClair

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.

JamalNUMAN

Thanks Robert.

Function wise:

Do compress and analyze tools improve view and edit performance?

Does rebuild indexes improve query performance?

Robert_LeClair

Jamal - function wise deserves an explanation:

The Compress GP tool does 2 things: it deletes orphaned lineages of states (i.e. edits) that are left behind after a Reconcile operation. These orphaned states may be seen in the States, States_Lineages, MVTables_Modified, and Delta tables. Second, it moves edits common to all versions to the Business (or Base) table - this empties the Delta tables for all versioned or versioned with the move to base option to the Base/Business table so 3rd party applications can "see" the data. As a result of this GP tool, one could say it improves view performance as the application does not have to traverse unnecessary records to show you the current view of a VERSION. Every time a user does a pan, zoom in, zoom out, etc. - the versioning tables are all queried. So fewer records in the versioning tables, faster query performance, faster display performance.
Rebuild indexes rebuilds attribute and/or spatial grid indexes built by ArcGIS (i.e. ObjectID) and those built by the user. Indexes are also rebuilt on repository tables owned by the SDE administrator that control versioned workflows. Attribute indexes are just that - they optimize attribute queries. Spatial grid indexes are used for draw performance in the map view. Spatial grid indexes may get out of date over time due to large data loads that change the average size of the features, the number of features in the feature classes change over time and the coordinate system of the feature class.
Analyze and Analyze Datasets rebuilds database statistics on feature classes/tables owned by the data owner as well as rebuilds statistics on the repository tables (owned by the SDE administrator). These statistics can include business tables, feature tables (for SDEBINARY), rasters, delta tables and archive tables (for the archive class created when Archiving is enabled). So again query performance here.

Hope this helps!

JamalNUMAN

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

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.