Enterprise geodatabases in SQL Server included with ArcGIS Server for Amazon Web Services

If you use ArcGIS for Server (Windows) Amazon Machine Image (AMI) to create an ArcGIS Server site, you have the option to include one of the following Microsoft SQL Server instances:

• SQL Server Standard
• Amazon Relational Database Service (RDS) for SQL Server
• SQL Server Express

When you create your instance using ArcGIS Server Cloud Builder on Amazon Web Services, the SQL Server instance contains two pre-created geodatabases: egdb and geodata.

The egdb geodatabase is registered as an ArcGIS Server managed database. When you publish feature or WFS-T services to a site that has a registered managed database, the data can be copied from the geodatabase that contains the map source data (publisher geodatabase) to the registered database (server geodatabase). This data is dependent on the service; when you delete the feature or WFS-T service, the data is deleted from the egdb geodatabase.

The geodata geodatabase is intended for use as a replicated geodatabase. You can register the geodata geodatabase with ArcGIS Server. When you do so, designate the geodata geodatabase as a server database connection that is not the same as your publisher database connection (your on-premises enterprise geodatabase) and create a geodata service. You can replicate data from your on-premises enterprise geodatabase to the geodata geodatabase through the geodata service.

When you publish a feature or WFS-T service that includes the replicated data, edits made to the data through the feature service can be synchronized with the geodata service, updating the data in your on-premises enterprise geodatabase. Similarly, you can continue to edit your on-premises data and use the geodata service to synchronize those changes to the data in the geodata geodatabase.

SQL Server Standard

If you choose SQL Server Standard, you can choose to create the DBMS on the same instance as ArcGIS Server or on an instance separate from your ArcGIS Server instance.

The SQL Server Standard instances are set to use mixed-mode authentication. They come with the following two operating system logins:

• Administrator: This login is the ArcGIS Server on Amazon Web Services instance administrator and an administrator in the SQL Server instance.
• ArcGIS: This login is an administrator in the SQL Server instance and is the login under which ArcGIS services run. This login must have access to the data to publish services.

Both logins are members of the SQL Server sysadmin fixed server role; therefore, the egdb and geodata geodatabases that are created by ArcGIS Server Cloud Builder on Amazon Web Services are stored in the dbo schema, and any data loaded while logged in as either of these users is stored in the dbo schema in each geodatabase. As dbo, these users have full privileges on all the data loaded to the geodatabases and the SQL Server instance itself.

The password for these logins are set by the system. You can alter the password for the Administrator login. See Changing passwords for the Windows Administrator for instructions.

If you manually create your site using the Amazon Web Services console, you must create your own geodatabases. You can use the Create Enterprise Geodatabase geoprocessing tool or Python script to do this. After the geodatabases are created, you must create ArcGIS users in the database for the ArcGIS login so you can publish services.

Amazon RDS for SQL Server

An Amazon RDS for SQL Server instance will always be created as an instance separate from your ArcGIS Server instance.

SQL Server RDS instances do not support operating system authenticated logins. When you create your site using ArcGIS Server Cloud Builder on Amazon Web Services, two SQL Server logins and database users are created.

• EsriRDSAdmin: The EsriRDSAdmin user is the RDS master user, which creates the databases and sde user. EsriRDSAdmin also owns the data that is copied to EGDBHOST when you publish feature services. ArcGIS Server Cloud Builder on Amazon Web Services sets the password for this account to be the same as the password you provide for the ArcGIS Server site administrator.
• Sde: The sde user owns the geodatabase system objects. ArcGIS Server Cloud Builder on Amazon Web Services sets the password for this account to be the same as the password you provide for the ArcGIS Server site administrator.

If you manually create your site using the Amazon Web Services console and want to use SQL Server RDS for data storage, you need to do the following to get your geodatabase set up:

• Use SQL Server Management Studio or TSQL to create a database.
• Use SQL Server Management Studio or TSQL to create an sde login, database user, and schema.
• Use SQL Server Management Studio or TSQL to grant the sde user sufficient privileges to create a geodatabase.
• Run the Enable Enterprise Geodatabase geoprocessing tool or Python script to create a geodatabase.
  Note:

  You cannot use the Create Enterprise Geodatabase geoprocessing tool or script to create an sde user and geodatabase in SQL Server RDS.

• Create a login, database user, and matching schema to load data, and grant the user privileges to create data. You can use the Create Database User or a Python script to do this, or you can use Management Studio or TSQL.
• Register your geodatabase with ArcGIS Server.

SQL Server Express

SQL Server Express instances are always created on the same instance as ArcGIS Server.

The SQL Server Express instances use Windows-authenticated logins exclusively. They come with the following two operating system logins:

• Administrator: This login is the ArcGIS Server on Amazon Web Services instance administrator and an administrator in the SQL Server Express instance.
• ArcGIS: This login is an administrator in the SQL Server Express instance and is the login under which ArcGIS services run. This login must have access to the data to publish services.

Both logins are members of the SQL Server sysadmin fixed server role; therefore, the egdb and geodata geodatabases are stored in the dbo schema, and any data loaded while logged in as either of these users is stored in the dbo schema in each geodatabase. As dbo, these users have full privileges on all the data loaded to the geodatabases and the SQL Server instance itself.

The password for these logins are set by the system. You can alter the password for the Administrator login. See Changing passwords for the Windows Administrator for instructions.