One issue with Archiving that prevents us from using it is the fact you are required to use the ObjectID field to store the relation between the main feature class and the history table,and how do you maintain the archive table if you need to delete the feature class temporarily and reload it for major schema changes. If I have to export all my data from SDE and completely rebuild the schema from a UML or ArcGIS Diagrammer, when I reload all the archiving kept in the history table after I disable archiving will be broken.
Am I missing something? I do not see a place to setup which field the archive uses to store the object in the table being stored.
Just to reiterate, the workflow would be:
-Begin with versioned/archived layer on SDE:
-Disable archiving, choose option to keep archive
-Export data from feature class to File Geodatabase or XML Recordset temporarily
-Delete feature class
-Load new feature class schema into SDE from xml
-Reload data into SDE from FGDB or XML Recordset
-Version
-Re-enable archiving
Now that JTX is moving to this as the sole option for storing edit transactions, this is going to be a problem if we decide to make changes to our 20+ layer utility network dataset