Creating a User and Configuring an Enterprise Geodatabase on MosaicGIS


As part of InterDev’s MosaicGIS new client onboarding process, an enterprise geodatabase is created and registered with ArcGIS Server. This knowledge base entry address that process.


This knowledge base article is geared toward the GIS Systems Administrator for MosaicGIS.


Knowledge of ArcGIS for Server and SQL Server plus administrative access to the MosaicGIS platform.


  1. Request that InterDev IT create new Active Directory user that is a member of the SG-GIS-TS USERS security group. If this user is assigned to a specific project, also request that three new security groups are created using the below schema. IT will create the groups while GIS will assign the appropriate permissions in SQL Server.
Group Name Description SQL Permissions Needed
SG-GIS-PROJECT NAME User may view data db_datareader
SG-GIS-PROJECT NAME-EDITOR User may edit existing datasets db_datareader, db_datawriter, EXECUTE
SG-GIS-PROJECT NAME-CREATOR User may create new datasets and edit existing datasets db_datareader, db_datawriter, EXECUTE, CREATE TABLE, CREATE PROCEDURE, CREATE VIEW
  1. As the enterprise geodatabases on Mosaic use the Dbo schema, the user you’d like to own the database will need to create the database. To accomplish this, ask the user who will need to own the database to temporarily change their AD password and provide you with their login credentials.

  2. Temporarily provide the database owner account with the sysadmin role.

  3. Create database via ArcGIS Pro or ArcMap. Creating the database using ArcGIS Pro makes it easier to obtain the connection file later, but ArcMap will work fine as well. the database name should follow the following schema, “projectnameProjectsubcategoryGIS”. Note the use of camel case. An example is provided below.

  1. Remove the database owner acount from the sysadmin role.

  2. Ask the database owner user to reset their password.

     **DO NOT SKIP STEPS #5 or #6**
  3. In SQL Server, add a new login under the Security Folder. Locate the appropriate AD security group, noting that the object type field must be altered to include Group and then location must be changed to If these parameters are not set, the security group will not be visible.

  1. Once the group is selected, map it to the appropriate database. Configure permissions per the table below step #1. Ensure that the User and Default Schema fields are the same.

  2. Configure any other permissions necessary based on the table below step #1 by right-clicking the database in question, clicking properties, clicking on the Permissions page, and finally selecting the security group that is being configured. There you will be able to make any changes needed. Once again, refer to the table below step #1 for specific permissions.

  1. Map the GISSQL\arcgis account to the new database within SQL Server and provide it with the db_datareader and db_datawriter roles. This allows the database to be registered with the server using a connection file that contains AD credentials.

  2. Export a connection file from ArcGIS Pro and register with ArcGIS Server via Server Manager.


Quality Control Checklist

  1. Connect to newly created eGDB.
  2. Create a new feature class & register it as versioned. If you run into an error, refer back to the table below step #1 and confirm permissions are set appropriately.
  3. Create new feature and save edits.
  4. Publish service to http://gis1:6080/arcgis/admin and ensure that the following error is not encountered, “Data source is not registered with the server and data will be copied to the server”. If it is, refer back to steps #7 - #10.

If any of the above steps are not successful, please check that all steps in the procedure have been followed correctly.

Was this FAQ helpful?
FAQ details:
Published date: 05/09/2017 2:04PM
Last updated: 25/09/2017 7:25PM (Chris Rice -
^ Top of Page