Available with Standard or Advanced license.
This tutorial presents an example of how you can get started using an enterprise geodatabase in PostgreSQL on a Microsoft Windows server. This tutorial assumes that you have already installed ArcGIS Server and ArcGIS Pro, and that you have connection information for both the database and geodatabase administrator logins.
Install and configure PostgreSQL
For this tutorial, you can run the PostgreSQL installation provided on My Esri or obtain a supported PostgreSQL version from another source. After PostgreSQL is installed, configure the database cluster to accept remote connections by altering the pg_hba.conf file.
Download and install PostgreSQL.
- Download the PostgreSQL installation from My Esri.
- Run the setup executable on the Windows server where you want to install PostgreSQL.
Other than setting the locale and collation for non-English language sites, you can use the default values provided in the installation wizard.
You will specify a password for the postgres superuser during the installation. Be sure to remember this password, as it is the database administrator password for the database cluster and will be needed later in this tutorial.
When PostgreSQL is first installed, you can only connect to it from the local server. To allow other machines on your network to connect, you must alter the pg_hba.conf file.
- In a text editor, open the pg_hba.conf file found in the PostgreSQL data directory.
The default location is C:\Program Files\PostgreSQL\<PostgreSQL version>\data.
- Specify the client addresses you want to access your database.
In the following example, all machines connecting from orgnetwor.com are allowed access to all databases on the database cluster:
#TYPE DATABASE USER ADDRESS METHOD host all all .orgnetwork.com md5
To make the database cluster more secure, you can restrict access to specific IP addresses or a range of addresses, specify a database or list of databases to which you want to grant access, or specify which users can connect. You can even explicitly disallow access to an IP address or range of IP addresses. See PostgreSQL documentation for more information and examples.
- Restart the PostgreSQL service.
You can do this by right-clicking the postgresql-x64 service in the Windows Services list and clicking Restart.
Place the ST_Geometry libraries in the PostgreSQL lib directory
You can use the ST_Geometry spatial type in the geodatabase or a PostGIS spatial type. For this workflow, you'll configure ST_Geometry.
You can obtain the ST_Geometry library file from the DatabaseSupport folder of an ArcGIS Server installation, or you can download the file from My Esri.
Because this tutorial assumes your PostgreSQL installation is on a Windows server, use the ST_Geometry library found in the Windows64 folder.
- In Windows Explorer, navigate to the location of the Windows ST_Geometry library in your ArcGIS client installation directory or download the file from My Esri.
- Copy st_geometry.dll from this location.
- Navigate to the PostgreSQL lib directory on the database server and paste the library to that location.
On Windows, the default location is C:\Program Files\PostgreSQL\<PostgreSQL version>\lib.
Create a geodatabase
You can use the Create Enterprise Geodatabase geoprocessing tool to create the database, sde user, sde schema, and a geodatabase in PostgreSQL.
- Start an ArcGIS Desktop client or ArcGIS Pro and open the Create Enterprise Geodatabase tool.
- Provide the information required to connect to the PostgreSQL database cluster as the postgres superuser to create a database and sde user. You must also point to the keycodes file that was generated when you authorized your ArcGIS Server site.
- Click Run.
The database, sde user, sde schema, and geodatabase are created in PostgreSQL.
Create a user to own data
Data stored in your geodatabase should be owned by users other than the sde user. Use the Create Database User geoprocessing tool to create a user in the PostgreSQL database cluster and a schema in your new database.
To create the user, though, you must first connect to the geodatabase as the database administrator. In this case, you can connect as the postgres superuser or the sde user, as the Create Enterprise Geodatabase tool granted the sde user superuser status.
Create a database connection, logging in as the postgres or sde user.
- Connect to the database by right-clicking the Databases folder in the Catalog pane and clicking New Database Connection.
The Database Connection dialog box appears.
- Provide the information necessary to connect to your new database as a PostgreSQL superuser.
Since you will use this connection file in a geoprocessing tool, you must check Save user name and password. After the tool is run, though, you should either uncheck this option in the connection file, connect as a different user, or delete the connection file to prevent other users with access to this file from logging in to the geodatabase as a database administrator.
- Click OK to create the connection.
A new connection file appears under Database Connections.
Now you can run the Create Database User tool.
- Open the Create Database User.
- Drag your new connection file into the Input database workspace text box on the Create Database User tool.
- Type a name for the new user in the Database User text box and a password for the new user in the Database User Password text box.
- Click Run.
A new user and schema are created in PostgreSQL, and USAGE is granted automatically on the schema to the public role.
Connect as the newly created user
Now that you have a user who can add data to your new geodatabase, connect to the database as that user. The easiest way to do that is to alter the connection file you created earlier.
Open the existing database connection and change the user name and password.
- Right-click your database connection and click Connection Properties.
- Change the User name and Password values to those of your new user.
- Click OK to connect as the new user.
You can now use this connection to add data to your geodatabase.