SQLite

The default scheduler database used by Data Reviewer Server is SQLite. SQLite is installed along with Data Reviewer Server. The server locates and uses the SQLite database automatically. You are not required to make any configuration changes to enable scheduler database storage in SQLite.

Each time you add the Data Reviewer Server capability to a map service and start that map service, Data Reviewer Server attempts to create a new SQLite database for that service. If a SQLite database already exists with that map service name, Data Reviewer Server will use it. SQLite databases are named after the map service that uses them (<map service name>.sqlite).

All SQLite databases are located in the ArcGIS Server user's appdata\Local\ESRI\Server<version>\schedule folder. For example: C:\Users\arcgis\AppData\Local\ESRI\Server<version>\Schedule.

SQLite databases are single files. You can back them up. You can copy them to other Data Reviewer Server instances to reuse the schedules defined in them as long as the map service name matches the SQLite file name.

Enterprise database

You can also store the scheduler database in either an Oracle, SQL Server or PostgresSQL-based enterprise relational database management system (RDBMS). This requires the following manual configuration steps:

• Install the RDBMS client software.
• Grant the ArcGIS Server user access to the location of the client software.
• Create the scheduler tables in your enterprise database.
• Type in a connection string to the enterprise database instance in a reviewer map service's capabilities page in ArcGIS Service Manager.

Using an enterprise database to manage and store the scheduler database has the following advantages:

1. The scheduler database can participate in database backup and restore operations.
2. Access to the scheduler tables can be managed with operating system or database authentication.
3. You can include the scheduler database in high–availability strategies like replication and log shipping.

Functional comparison

SQLite works well in single-server deployments where enterprise relational database management system (RDBMS) functionality is not required. Store the scheduler tables in Oracle, SQL Server or PostgreSQL when you require enterprise RDBMS capabilities. The following table summarizes each choice by functional area.