To minimize the number of rows created in the database while performing versioning workflows (loading, quality checking, reconciling, and posting),Traditional versioning without the archiving optionis the best choice.
1. Traditional Versioning Without Archiving
* This method stores edits indelta tables(Adds and Deletes) rather than directly in the base table.
* Without the archiving option, the system does not create additional rows to track historical changes, which helps reduce the number of rows.
2. Why It's Ideal for This Workflow
* Load Data: Data is directly inserted into the delta tables, keeping base tables untouched.
* Quality Verification: Edits can be reviewed and adjusted without additional overhead.
* Reconcile and Post: Only the changes made during the session are pushed to thedefault version, and unnecessary rows are avoided.
3. Why Not Other Options?
* Traditional Versioning with Archiving Option:
* Archiving tracks historical changes, creating additional rows for each edit in the archive tables.
This increases storage and processing overhead.
* Branch Versioning:
* Branch versioning stores all changes in a single table and is designed for web services workflows.
It may not minimize row creation compared to traditional versioning.
Steps for the Workflow:
* EnableTraditional Versioningfor the target dataset without enabling archiving.
* Load the large dataset into a new version created for this purpose.
* Verify the data quality by querying and editing the version.
* Reconcile the version with the default version, resolve conflicts, and post changes to default.
References from Esri Documentation and Learning Resources:
* Understanding Traditional Versioning
* Archiving in Enterprise Geodatabases
* Branch Versioning vs. Traditional Versioning
Conclusion:
UsingTraditional versioning without the archiving optionensures the creation of the fewest number of rows while maintaining data integrity and supporting the described workflow.