Importing condition tables into Execute SQL checks

Condition tables can be migrated to Execute SQL checks. The Execute SQL check provides a means of accessing and maintaining the parameters. During migration, each WHERE clause and feature class combination specified in the condition table is used as criteria for the Execute SQL check.

An Execute SQL check created from a condition table record

The end result is a check that encapsulates information from the condition table stored in a batch job that can be run using Reviewer Batch Validate. Since the checks are included in a Reviewer batch job, you can also run the batch job using the Reviewer Batch Validate tool.

Learn more about running Reviewer batch jobs

Steps:

1. Start ArcMap.
2. On the main menu, click Customize > Toolbars > Data Reviewer.
3. Click the Reviewer Batch Job Manager button on the Data Reviewer toolbar.

   The Reviewer Batch Job Manager dialog box appears.

4. Click Import CNTs.

   The Select Workspace dialog box appears.

5. Navigate to the geodatabase that contains the condition table to import.

   This geodatabase must have all the knowledge base tables to run a CNT check, PLTS_MASTER_CNT, PLTS_Errors, and DBS_FC_VVT. Also, the data that the CNT checks are validating must be in the geodatabase.

6. Click Select.

   The condition table records are imported and converted to individual Execute SQL checks. When the process is complete, the top part of the dialog box lists the checks that have been created. They are grouped by feature class.

7. Click Save As.

   The Save As dialog box appears.

8. Type a name for the batch job in the File name text box.
9. Click Save.

   The Reviewer Batch Job Manager dialog box appears.

10. Click OK.