idea Re Associate Archive Tables in Data Management Ideas

Re Associate Archive Tables

TedCronin — Wed, 24 Aug 2022 21:15:44 GMT

It would be nice to have the capability to re associate archive tables after a database has been unversioned. Currently, I need to back up this history every time I take my system completely down, which happens once per year every year, so basically I have a File GDB with all of this history. It would be nice to not have to take the data out and just reconnect it back to the FCs once my schema changes have been completed.

Re: Re Associate Archive Tables

JamesKyle — Tue, 14 Feb 2012 18:01:42 GMT

It would a good idea for various other reasons as well. There always will be situations when there are changes required to your data model that may require archving to be turned off temporarily.

Re: Re Associate Archive Tables

BillMyers — Fri, 02 Nov 2012 00:03:42 GMT

An excellent idea! Without this added capability geodatabase archiving is very cumbersome to manage and is marginally useful.

Re: Re Associate Archive Tables

mrasiukevicius — Wed, 21 Oct 2015 08:59:05 GMT

Archiving is an old functionality of Geodabase. But there is no way to re-enable archiving using ArcGIS tools. There should be a possibility to re-enable archiving if for some reason archiving was disabled.

It is a real pain if for some reason archiving should be disabled (disable versioning, db structure changes, migration etc.). There should be out of the box solution to re-enable achiving ArcGIS way. - See more at: https://c.na9.visual.force.com/apex/ideaView?id=087300000008G3l&mc=0#sthash.f87p0JoP.dpuf

Tool to re-attach archive tables

KevinDunlop — Wed, 17 Aug 2022 03:57:05 GMT

Currently, when you disable archiving in SDE, you can choose to save the history table as a new feature class. However, there is no way to re-attached that saved history table when you re-enable archiving. This is a problem when you need to briefly turn off archiving to make changes to the layer or to copy it from one database to the other. If there was a tool to re-attach the archive table to the feature class, it would allow for a more complete archive history. This could cause a "false gap" in the history if edits were made during the time archiving was turned off, but the DBA should still be given the option.

An additional option to this solution would be to allow the user to attach multiple archiving table. This way the DBA could save off each year as a new archive table but still be able to attach them as needed. In this case, the tables would be attached to the historical version tree but the records would not be imported into active archive table.

Re: Tool to re-attach archive tables

DurpheyClifton — Tue, 22 Jun 2021 08:55:01 GMT

This is a similar idea to the following posts:

Re Associate Archive Tables

https://community.esri.com/ideas/2650

Keeping a true history of an asset's history would require that the information be located in one spot and not across several standalone tables. Administrators will inevitably have to turn off archiving and unregister data as versioned in order to do maintenance.

This feature would help to make a GIS database more of a true asset register.

Re: Tool to re-attach archive tables

BlakeTerhune — Mon, 22 May 2017 21:39:30 GMT

Related discussion.

https://community.esri.com/thread/19762

Re: Re Associate Archive Tables

BlakeTerhune — Mon, 22 May 2017 21:40:43 GMT

Related discussion.

https://community.esri.com/thread/19762

Geodatabase Archiving workaround solutions

Anonymous User — Wed, 17 Aug 2022 04:05:02 GMT

Hi,

We have various geodatabases that need to be saved. To do this, Arcmap has a built-in functionality called Archiving. This is very good functionality as long as we don't have to make major changes to the system, such as adding layers, tables, topology, and so on. In order for the changes described above to take effect, archiving must be turned off and choosing to keep the archiving tables will remain at the database level, with no real connection. However, if we turn it back on, new tables will be created and will no longer be merged with existing ones. I've seen workrounds in various forums, but because we have a constantly evolving geodatabase structure, all solutions are very time consuming and can break things down in the wrong order. For example:

https://gdbgeek.wordpress.com/2011/11/22/restoring-geodatabase-history/

Perhaps there are more sensible ways for such a workflow to make all bigger changes and reconnect old archiving data in less time. Maybe create an additional option in Archiving to merge with existing tables? I know that I am not only who struggles with this problem.

Thank you!

BR,

Tiina Arras