Currently our organization has a few datasets on 10.0 SDE, but many are in project folders as shapefiles and geodatabses. We recently added new servers that has a single 10.1 SDE. We're hoping to move all our project data and base layers to the 10.1 SDE and are trying to determine the best way to organize the 10.1 SDE "Data Center". We're trying to avoid having multiple SDE's for each project and departments.
I've attached a PDF with how we want to structure our 10.1 SDE but we would like to get some recommendations/advice if this isn't the best possible organization structure. Ideally, we'd like to have a main "Data Center" with the GIS Team as administrators with complete access to edit the feature datasets. We're planning to give each department only privileges to their feature dataset. For example, Department 1 would only be given privileges to the Dept1.Transportation feature dataset.
Would we be running into any complications with domains/subtypes, versioning, archiving and editing with this set up? We do have some non-GIS professionals that do their own data entry working with an shapefiles/geodatabases. If we migrate all project data and base layers onto the same SDE would this cause complications? Right now we don't enable versioning but that is an ArcSDE function we'd like to begin utilizing. We're concerned with departments accidentally reconciling/posting each others feature classes.
Any recommendations would be greatly appreciated. Thank you in advance!
I've attached a PDF with how we want to structure our 10.1 SDE but we would like to get some recommendations/advice if this isn't the best possible organization structure. Ideally, we'd like to have a main "Data Center" with the GIS Team as administrators with complete access to edit the feature datasets. We're planning to give each department only privileges to their feature dataset. For example, Department 1 would only be given privileges to the Dept1.Transportation feature dataset.
Would we be running into any complications with domains/subtypes, versioning, archiving and editing with this set up? We do have some non-GIS professionals that do their own data entry working with an shapefiles/geodatabases. If we migrate all project data and base layers onto the same SDE would this cause complications? Right now we don't enable versioning but that is an ArcSDE function we'd like to begin utilizing. We're concerned with departments accidentally reconciling/posting each others feature classes.
Any recommendations would be greatly appreciated. Thank you in advance!
If feature datasets, realize that you cannot control permissions to individual featureclasses in a feature dataset.
Ideally, and if you can, load all data with a single account. Create a GIS Team role, give that role edit permissions to all featureclasses, add GIS Team members to that role.
The owner of the version can reconcile/post that version. You might consider setting the Default version access to Protected.