Trim Archive History Tool for Branch Versioned Data

[ScottNoldy]

To add another use case:

Feature class is versioned/archived/branch versioned simply to allow offline use in Collector.

Feature class is updated nightly from another database so every night, another row is added for each record to the dataset.  The dataset eventually grows extremely large killing performance.

Something similar to the Trim Archived feature class would be ideal.

[ScottNoldy]

The below comments were moved from a separate Idea, to more accurately reflect the work under consideration by the development team.

[ToddW_stl]

@SSWoodward - it looks like this has been released and is available now, can you confirm?  Although this thread's title is a bit confusing since it mentions branch versioning.

"To decrease the size of these tables, you can use the Trim Archive History geoprocessing tool to delete retired rows from nonversioned archived datasets without disabling archiving or disrupting sync workflows in your enterprise geodatabase."

I would think the branched versioning flavor of this tool is Prune branch history, if you can also comment/confirm my thinking on this.  Thank you!

[SSWoodward]

Thanks @ToddW_stl,

That's correct! In ArcGIS Pro 3.5 users have access to the new Prune Branch History geoprocessing tool that allows the ability to prune rows from their branch history that are no longer referenced by any versions or replicas.

Let us know how the tool works for you!

[lah]

Curious if anyone has had any success with the new Prune Branch History tool? We are testing 11.5/3.5 and cannot get it to run successfully on a feature dataset in SQL EGDB. 

[SSWoodward]

A @lah are you able to DM me your log file?

[ToddW_stl]

@lah - I was able to get it to work at 11.5/3.5.x on a SQL EGDB.  @SSWoodward should be able to help if you're able to provide the log file.  It was a little confusing that I had to uncheck both Report Only AND Only Prune System Tables checkboxes to get it to work.  Report Only is listed as optional in the docs, which makes sense, but I didn't quite understand what the other check box is doing.

[RobertKrisher]

@ToddW_stl when the second checkbox is checked it will cause the tool to only prune system tables, while leaving user data (i.e. the tables you can see in Catalog) untouched. This is important for some users who need to retain a longer history for edits made to user data (parcels, transformers, etc) for regulatory reasons but still want to prune system tables (like dirty areas or the network topology) more aggressively.

[SSWoodward]

Thanks for everyone's comments here. 

After chatting with @lah on the side, we determined the issue was that the feature dataset contained a controller dataset which is not yet supported by the prune branch history tool.

Prune branch history supports Utility Networks, and Topologies.  Support for additional controller datasets are not currently implemented. 

For more information on the tool and its current functionality, check out the core documentation or this recent blog, Prune like a Pro, for additional details.