Recommended SDE database maintenance in branch versioning environment

[Brian_McLeer]

We are using branch versioning for the first time in an SDE database (SQL Server 2016). 

For our existing traditional versioning DBs, we use the recommended compress, rebuild indexes, and analyze datasets in our nightly routines similar to ESRI documentation below. This methodology is not recommended with branch versioning, however. 

Is anyone using certain GP tools on a regular basis for database maintenance for an SDE database that uses branch versioning? If so, what methods are you using? Do branch versioned DBs require daily maintenance as traditional versioned DBs require?

Enterprise geodatabase maintenance tasks—Manage geodatabases in SQL Server | Documentation 

[AmandaBishop2018]

Hello Brian,

We are also in the same boat as of a few weeks ago and we are experiencing some issues with latency.  Did you ever get an answer for your question?

Amanda

[DanielWebb]

I would also like to know more about this topic.

[Colin_Zwicker · Accepted solution]

Brian (and all curious),

Branch versioning is still built on top of the underlying dbms table structures and utilizes the dbms indexes to optimize access paths. Therefore the standard dbms maintenance tasks (rebuild indexes, and analyze datasets) apply. 

The pattern of enterprise geodatabase maintenance that is not required compared to Traditional versioning is that of Compress.

In addition you should monitor how many offline services (sync replicas) you are currently supporting and decide if they still have value.

Thanks,

Colin