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 a Microsoft SQL Server Standard or Express instance. If you choose a SQL Server Standard instance, you have the additional option of creating the DBMS on an instance separate from your ArcGIS for Server instance.

The SQL Server instances contain 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.

The egdb and geodata geodatabases are both stored in the dbo schema.

The SQL Server Express instances use Windows-authenticated logins exclusively. The SQL Server Standard instances are set to use mixed-mode authentication. Both instances come with the following two operating system logins:

Both logins are members of the SQL Server sysadmin fixed server role; therefore, 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.

12/10/2013