Adding a Stand Alone Table Validation - Teradata Ecosystem Manager

Teradata® Ecosystem Manager User Guide

Teradata Ecosystem Manager
Release Number
December 2020
English (United States)
Last Update
Product Category
Analytical Ecosystem
  1. Click Tables.
  2. Click the name of the table you want to validate.
  3. Click the Validation tab.
  4. Click next to Stand Alone Validation.
  5. [Optional] Click to schedule the validation.
    For example, you can assign the validation to occur the first day of every month at 12 am.
  6. [Optional] Enter a statement in the WHERE clause to define partial table validation.
    Use the Where Clause Helper to select columns:
    1. Click to see a list of column names, and then select a column. Use the control or shift key to select multiple columns.
    2. Click to insert the columns into the Where Clause.
    For example, to include only rows that are more than or equal to 100 in column_01, the statement is: column_01>=100
  7. Select one or both of the table validation techniques:
    Validation Technique Description
    Row Count flag Select the Row count flag box to verify whether the row count of a table matches across the Teradata Database.
    Validation Expression Enter a custom table validation expression (up to 500 characters). You can use the Validation Expression Helper:
    1. Click next to Validation Expression.
    2. Select a function.
    3. Select a column. Use the control or shift key to select multiple columns.
    4. Click to insert the column.
    For table validation on Hadoop or Aster systems, the validation expression technique is not available. For Hadoop systems, see Adding a Stand Alone Hadoop Table Validation.
  8. [Optional] If you check the Row count flag, choose how to define validation failure.
    • Use base tables rules. Base table rules are global rules defined in the Manage Synchronization Rules view.
    • Use a custom rule to enter the limit for the row count difference across systems. You can enter a whole number or a percent value with decimals. For example, 1,200, 10% or 5.23% are acceptable.
  9. Set up an alert if validation fails.
  10. [Optional] Check freeze and activate Unity-managed tables when the validation runs.
    See About Table Validation for information on this feature.
  11. [Optional] Override default system selections and credentials.
    This allows you to enter a different database user.
  12. Click Test to verify the validation.
    Test is not available for table validation involving Hadoop or Aster systems.
  13. Click Apply for the changes to take effect.