To ensure that editing and public usage do not affect each other, the best approach is tocreate separate database instancesfor these purposes.
1. Why Separate Database Instances?
Performance Isolation: Separating the databases ensures that editing operations (which are resource-intensive) do not impact the performance of queries or map services used by the public.
Workload Management: Editors can work in a dedicated environment with optimized settings for editing, while the public-facing database can focus on efficient querying and read-only access.
Security and Data Integrity: Public users are isolated from the editing environment, reducing the risk of unauthorized changes or accidental data loss.
2. How Separate Instances Work
Primary (Editing) Database: This instance supports editing workflows, including versioning, replication, and real-time updates.
Replica (Public) Database: A replicated copy of the primary database is maintained for public usage. Updates can be synchronized periodically using one-way or two-way replication.
3. Why Not Other Options?
Build New Feature Datasets:
Feature datasets organize related feature classes but do not separate editing and querying workloads. Performance issues would persist.
Separate Permissions for Public Services:
While restricting permissions helps secure data, it does not address performance issues caused by concurrent editing and public queries on the same database instance.
Steps to Create Separate Instances:
Set up aprimary database instancefor editing workflows.
Create areplica database instancefor public use by:
Using one-way replication to push updates from the primary to the public database.
Configuring the replica as read-only for public access.
Monitor and optimize each instance independently to ensure optimal performance.
References from Esri Documentation and Learning Resources:
Geodatabase Replication for Distributed Workflows
Managing Performance in Enterprise Geodatabases
Conclusion:
Creatingseparate database instancesensures optimal performance by isolating editing workflows from public usage, addressing both performance and security concerns.
