Is This Content Helpful?
We're glad to know this article was helpful.
Poor multi-version SQL performance when doing versioned queries. The following procedures are suggestions to maintain SQL performance with versioned queries.
A multi-versioned table is analyzed when the table is first registered as versioned. From that point on ArcSDE does not analyze the table, the DBA is responsible for it.
Once the database is being used in a production environment, the number of rows in the table can grow significantly.
If the database's statistics for the table are not current and accurate, the instance's optimizer might choose a sub-optimal execution plan for fetching rows. This can have a negative affect on all version queries.
Based on the frequency of edits to the mulit-versioned table during editing, the DBA will need to analyze both the add and delete tables. This can be accomplished in a number of ways.
sdetable -o update_dbms_stats -t <table_name> -u <DB_user_name> -p <DB_User_password>
ANALYZE TABLE <table_name> COMPUTE STATISTICS;