ArcGIS Pro users needUndo/Redo functionality, which is available in versioned workflows.
SQL users also need to edit the dataset, requiring direct access to the database tables.
These requirements point to a need for a versioning method that supports both ArcGIS client workflows and SQL-based edits.
Versioning Methods Overview:
Nonversioned Editing:Nonversioned editing allows direct editing of the database but does not support Undo/Redo functionality in ArcGIS Pro, making it unsuitable for this scenario.
Traditional Versioning:
Supports Undo/Redo functionality for ArcGIS Pro users.
Stores edits in delta tables (adds and deletes) to manage versions.
SQL users can access and edit the base tables, making it compatible with their needs.
Branch Versioning:Branch versioning supports modern workflows and web services but requires a service-based approach for editing. It does not allow direct SQL edits, making it unsuitable for this scenario.
Steps to Implement Traditional Versioning:
Enable traditional versioning on the dataset in the enterprise geodatabase.
Ensure appropriate permissions are set for SQL users to access and edit the base tables.
ArcGIS Pro users will work in the versioned environment, allowing Undo/Redo operations during their edits.
References:
Esri Documentation: Understanding Versioning.
Traditional Versioning Concepts: Best practices for using traditional versioning with multiple user types.
Why the Correct Answer is B:Traditional versioning fulfills both requirements: Undo/Redo functionality for ArcGIS Pro users and SQL accessibility for direct edits.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit