Databases

If you use database authentication, the database user name and password you provide when you register the database is used to authenticate the connection.

If you use operating system authentication, the service connects to the database using the ArcGIS Server account. For ArcGIS Server sites running on Microsoft Windows machines, this is the login that runs the ArcGIS Server Windows service. For ArcGIS Server sites running on Linux machines, this is the account you signed in with when you installed ArcGIS Server.

The user or ArcGIS Server account must have privileges to connect to the database and select data to be published. If you publish editable feature services, the database user or ArcGIS Server account also must have privileges to edit the published data.

See the following information in the ArcGIS Pro help to determine the privileges the registered user or ArcGIS Server account requires to allow web services to access data in a database.

For read-only services (map services or feature services that do not have editing enabled), grant the privileges required for a data viewer. For editable feature services, grant the privileges required for data editors.

• Privileges for using ArcGIS with Dameng
• Privileges for using ArcGIS with a Db2 database
• Privileges for using ArcGIS with an Informix database (opens ArcMap help)
• Privileges for using ArcGIS with an Oracle database
• Privileges for using ArcGIS with a PostgreSQL database
• Privileges for using ArcGIS with an SAP HANA database
• Privileges for using ArcGIS with a SQL Server database
• Privileges for using ArcGIS with Teradata

Cloud data warehouses

Authentication methods for cloud data warehouses are different from those used for databases. However, the credentials you provide when creating the database connection file must have privileges to select the data to be published. If you create a materialized view when publishing, the credentials must have privileges to create a materialized view in the cloud data warehouse.