Hi Team,
Following is the requirement, As a Cartography Team(13 users ) want a playground for their GDB updates, edits, and deletes purpose. We have SQL Server with ArcGIS Sevrer Enterprise 10.8.1. All users conneccting to GDB with OS authentication with their organisation credentials.
Users want a GDB that's only visible to cartography Team.
1.users of the group can create/Update a new dataset without making it visible for all current arcgis pro users.
2.Make changes to the Data Model Without heavy impact on other datasets (we are going to consume feature classes from other GDB also)
3.Once it's confirm by business it will reconsile & post to master version by one of the Cartography Team member(one person shall have the credentials to reconsile & Post)
4.All 13 members can create 13 child versions & play with their respective Versions.
It would be highly appreciate for any suggestion .
There may be something I'm missing, but schema changes have to be made by an admin user, not data editor. Schema changes apply to the default version as well as any child versions (see here), so there is no way to silo such changes. Either a test geodatabase to be updated by all users (requires granting all Cartography users admin privileges) could accomplish this or each user stores a copy of the production geodatabase in a file geodatabase. The second option is not ideal as over time, each user's version of the geodatabase will differ from the others as well as the production. I would recommend a change management process where there is one database admin who implements the schema changes after testing them in a non-production environment. The Cartography team could still evaluate their changes on a fgdb copy of the production they store locally.