Our organization has been running an environment that has three different SQL Server databases
- Editing
- Viewing
- Field Work
Editing is where we update our core asset information. It's only accessible within our firewalls, and it currently edited with connection files in ArcGIS Pro. It uses traditional versioning. We treat this database as our primary, and have historically limited access to only GIS staff.
Viewing is populated with data from Editing, which is replicated nightly. This database is used to create web services on ArcGIS Server for our viewer apps, which we share across the organization or to the public.
Field Work is also populated with data from Editing, also replicated nightly. But this database also has tables and views that support field operations (inspections, maintenance, etc).
We have a new directive where we need to allow users to update our core assets in the field. I'm looking into shifting Editing from traditional versioning to branch versioning, and then serving that data through ArcGIS Server/Enterprise for edits. We also see the writing on the wall, that branch versioning is where Esri is focusing future development.
Are there any security or performance issues that I should be aware of before I go down that path? How would I handle replication?
