ArcGIS Data Reviewer for Server supports automated data validation. Automated validation can execute on demand or based on a schedule. Scheduled validation requires a database in which execution schedules are stored.
The scheduler database stores a series of scheduler tables and triggers. Data Reviewer for Server writes scheduled validation job information into these tables. It queries these tables to determine when to execute the next automated validation. Over time, validation job information is removed from these tables.
Data Reviewer for Server can store its scheduler tables in the following database types:
- SQLite
- Oracle
- SQL Server
- PostgreSQL
SQLite
The default scheduler database used by Data Reviewer for Server is SQLite. SQLite is installed along with Data Reviewer for 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 for Server attempts to create a new SQLite database for that service. If a SQLite database already exists with that map service name, Data Reviewer for 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 for Server instances to reuse the schedules defined in them as long as the map service name matches the SQLite file name.
Caution:
You cannot use SQLite as the scheduler database in an ArcGIS Server cluster or for map services configured in low isolation.
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:
- The scheduler database can participate in database backup and restore operations.
- Access to the scheduler tables can be managed with operating system or database authentication.
- You can include the scheduler database in high–availability strategies like replication and log shipping.
Note:
You must store the scheduler database in a supported enterprise database if your Data Reviewer for Server site participates in an ArcGIS Server cluster or map services are configured in low isolation.
Supported database versions
Data Reviewer for Server supports the following database platforms.
| Database | Operating System |
|---|---|
Microsoft SQL Server 2008 R2 and Microsoft SQL Server 2012 | Windows Server 2012 |
Oracle 11.2.0.1 (64-bit) and Oracle 12 | Windows Server 2012 Note:Microsoft .NET Framework 3.5 is required to support an Oracle-based scheduler database. |
PostgreSQL 9.4.5, 9.3.10, 9.2.14 (64 bit) | Windows Server 2012 |
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.
| Functional area | SQLite | Enterprise database |
|---|---|---|
Requires manual installation and configuration of database client software | No | Yes |
Requires manual configuration in ArcGIS Server Manager | No | Yes |
Supports ArcGIS for Server cluster | No | Yes |
Supports map services in low isolation | No | Yes |
Supports database authentication | No | Yes |
Supports enterprise database backup and restore | No - can be backed up as a single file | Yes |
Supports database-managed high-availability strategies | No | Yes |