Latest Contributions by KimPeter

Hi Sorato, If you're wondering about the registration options in ArcGIS Server Manager specifically, registering a managed database here means you provide and maintain an enterprise geodatabase into which data will be copied when you publish a feature service to that stand-alone ArcGIS Server site.  (In ArcGIS Pro, you need to choose the Copy data option when publishing.) Publishing to an ArcGIS Server site that has a managed database that you provide is a narrow use case.  A managed database is useful when you need to get on-premises data into a geodatabase in the cloud or outside your firewall. When you publish a feature service to an ArcGIS Server site that has a managed database, the data is copied from the source into the managed database. The service accesses the data that was copied to the managed database, not the source data. Registering a database with the ArcGIS Server site is a far more common workflow. You would do this any time you want the services on your ArcGIS Server site (stand-alone or federated) to access the source data in your enterprise geodatabase or database. The data stays in this database and is not copied when you publish. (In ArcGIS Pro, you need to choose to reference registered data when you publish.) That means people who work with the data through a database connection and those who access the published services are working with the same data. ... View more

No worries, Luyang. 🙂 Will you load data for faculty and students to use?  Or maybe faculty will load the data that students use? Whoever creates or loads data to the geodatabase will require permission to connect to the database, create table, create procedure, and create view privileges in the database, and will need a schema in the database that has the same name as their user name. If there will be multiple people creating/loading data, create a database role, grant the privileges to the role, and add the necessary users to that role. Each user who creates data will still need a matching schema, but using a role simplifies managing privileges.   Privileges for different types of geodatabase users can be found in this topic: http://resources.arcgis.com/en/help/main/10.2/#/User_privileges_for_geodatabases_in_SQL_Server/002q0000002s000000/ If students are loading the data, publishing it, and editing it, grant them the privileges of a data creator and they'll be able to do what they need with their own data.  If they need access to data someone else loaded, privileges must be granted to them on the individual datasets.  (Again, if a group of students all need the same privileges on a dataset, create a role with those privileges and add the students' users to it.)  Since you said you'll be using versioning and you may well be using other geodatabase functionality that involves system tables or procedures, grant dataset privileges through ArcGIS, not directly in the database. When done through ArcGIS, privileges are granted to all the tables, procedures, and views that make up a versioned geodatabase dataset.   You can use the Privileges dialog box in ArcGIS Desktop to do this - http://resources.arcgis.com/en/help/main/10.2/#/Granting_and_revoking_privileges_on_datasets/002q0000002z000000/ - or the Change Privileges geoprocessing tool, which can be scripted, if you need it: http://resources.arcgis.com/en/help/main/10.2/#/Change_Privileges/0017000000n3000000/. When publishing data, you have to think about the privileges of the person doing the publishing (they have to have access to the data to publish it) AND the privileges of the user that is specified in the .sde file you registered with ArcGIS Server. All the services will access the geodatabase data as the user in the registered .sde file.  Therefore, to publish a map service (or any other read-only service), connect permission to the database and select privileges on the datasets are required for:   -The user making the map (or accessing the data to be published)   -The user you have in the Database Connection file (.sde) that you registered with ArcGIS Server. *Be aware that if you use Windows-Authenticated logins, the ArcGIS Server primary site administrator (that's the administrator account created when you set up the ArcGIS Server site) needs the same privileges: in this case, connect permission and select privileges on the datasets. For services that allow you to edit or load data, such as editable feature services or image services, the privileges you grant to the user in the registered .sde file must be sufficient to perform the editing or data loading (image service) operations that you choose when publishing these services. For example, if you choose Query, Create, and Update operations for your feature service when publishing, the user needs select, create, and update privileges on the data that is in the service. Again, if using Windows Authentication, the ArcGIS Server primary site administrator also needs these privileges on the data. As you read in the topic Copying data to the server automatically when publishing, you could also register an enterprise geodatabase as your managed database. Then, when feature services are published, the data gets copied from your source to the managed database.  The data is owned by the user in the .sde file that you registered as the managed database. Therefore, that user needs privileges in the managed database sufficient to create data and a matching schema in the database.  The data in the managed database is dependent on the feature service: if you delete the feature service, the data is deleted from the managed database. Sorry...this is getting crazy long winded... On the versioning side, as mentioned, granting privileges on the versioned datasets through ArcGIS grants the privileges needed on the delta tables and versioned view.  Separate from that, geodatabase versions have coarse-grained permissions that the version owner can set to determine who has access to the version.  That is described here: http://resources.arcgis.com/en/help/main/10.2/#/Creating_versions_and_setting_permissions/003n000000ws000000/.  Your students might connect to a different version of the geodatabase and publish that data. The access level they set on that version could impact whether the published data can be edited. For example, if the version is protected but the .sde file registered with ArcGIS Server connects as someone other than the version owner or the geodatabase administrator, you won't be able to edit through the service. You also mentioned using replication...for an overview of how geodatabase replication and ArcGIS Server are related, see this topic: http://resources.arcgis.com/en/help/main/10.2/#/Geodatabase_replication_and_ArcGIS_Server/003n000000rn000000/ Basically, it involves using a geodata service, so see the topics in the Geodata services section of the ArcGIS Server help for information on using those: http://resources.arcgis.com/en/help/main/10.2/#/What_is_a_geodata_service/015400000329000000/ Phew.  I hope at least some of this is helpful. 🙂 @Marco: thanks for answering the subsequent post...it took me so long between meetings, etc. to compose the other answer, I missed Michael's question. ... View more