Skip To Content

Create scheduler tables in an enterprise database

Hinweis:

ArcGIS Enterprise 10.9.x, part of the ArcGIS 2021 releases, are the last ArcGIS Enterprise releases that support services published from ArcMap. You are encouraged to migrate automated review workflows to ArcGIS Data Reviewer capabilities available in ArcGIS Pro attribute rules.

The Data Reviewer ArcMap runtime-based server object extension (SOE) allows you to schedule batch validation to execute repeatedly according to a schedule. Schedules are stored in a database. By default, the Data Reviewer server extension uses SQLite to store and manage its schedules. However, you can store the scheduler tables in Microsoft SQL Server, PostgreSQL, or Oracle. If you choose to store the scheduler tables in one of these databases, you must manually create these tables using the process described below.

Hinweis:

These steps are optional. You only need to perform these steps if you want to store your scheduler tables in SQL Server, PostgreSQL, or Oracle. The following process pertains to SQL Server only.

  1. Open SQL Server Management Studio.
  2. On the Connect to Server dialog box, perform the following steps:
    1. Click the Server type drop-down arrow and choose Database Engine.
    2. Click the Server name drop-down arrow and choose a server to store the scheduler tables.
    3. Click the Authentication drop-down arrow and choose an authentication type.
  3. Click Connect.
  4. On the main menu, click the File Open button Datei geöffnet.
  5. Browse to the location of the tables_sqlServer.sql file.

    This file is located in <ArcGIS server installation location>\ArcGISDataReviewerServer\Server<version>\sql\creation_scripts.

  6. Click Open.

    The contents of the file load into the query window.

  7. At the top of the file, change [enter_db_name_here] to the name of the database that will store the scheduler tables.

    Example: USE [drs_scheduler]

  8. Click Execute to run the SQL statements.

    The scheduler tables are created in the database.