Skip to content

Last updated: July 05, 2025

How to Monitor Teradata? Data Observability Configuration

Learn how to monitor Teradata and enable data observability to detect schema changes, data anomalies, volume fluctuations, and data quality issues.

Overview

Teradata provides the most flexible analytical engine in the most scalable and manageable database for your data warehouse.

DQOps free version limits

Teradata drivers are not provided in an open-source version.

For more details, please contact DQOps sales.

Add a Teradata connection using the user interface

To navigate to the Teradata connection settings:

  1. Go to the Data Sources section and click the + Add connection button in the upper left corner.

    Adding connection

  2. Select Teradata database type.

    Selecting Teradata database type

Fill in the connection settings

After navigating to the Teradata connection settings, you will need to fill in its details.

Adding connection settings

Teradata connection settings Property name in YAML configuration file Description
Connection name The name of the connection that will be created in DQOps. This will also be the name of the folder where the connection configuration files are stored. The name of the connection must be unique and consist of alphanumeric characters.
Parallel jobs limit A limit on the number of jobs that can run simultaneously. Leave empty to disable the limit.
Host host Teradata host name. Supports also a ${TERADATA_HOST} configuration with a custom environment variable.
Port port Teradata port name. The default port is 1025. Supports also a ${TERADATA_PORT} configuration with a custom environment variable.
User name user Teradata user name. The value can be in the ${TERADATA_USER} format to use dynamic substitution.
Password password Teradata database password. The value can be in the ${TERADATA_PASSWORD} format to use dynamic substitution.
JDBC connection property Optional setting. DQOps supports using JDBC driver to access Teradata. See the Teradata documentation for JDBC connection parameter references.

DQOps allows you to dynamically replace properties in connection settings with environment variables. To use it, simply change "clear text" to ${ENV_VAR} using the drop-down menu at the end of the variable entry field and type your variable.

For example:

Adding connection settings - environmental variables

To add optional JDBC connection properties, just type the JDBC connection property and the Value. The value can be in the ${ENVIRONMENT_VARIABLE_NAME} format to use dynamic substitution.

For example:

Adding connection JDBC settings

To remove the property, click the trash icon at the end of the input field.

After filling in the connection settings, click the Test Connection button to test the connection.

Click the Save connection button when the test is successful otherwise, you can check the details of what went wrong.

Import metadata using the user interface

When you add a new connection, it will appear in the tree view on the left, and you will be redirected to the Import Metadata screen. Now we can import schemas and tables.

  1. Import the selected data resources (source schemas and tables) by clicking on the Import Tables button next to the name of the source schema from which you want to import tables.

    Importing schemas

  2. Select the tables you want to import or import all tables using the buttons in the upper right corner.

    Importing tables

Upon import, you will receive information that a new tables have been imported. You can then begin collecting basic statistics and profiling data by running default data profiling checks. Simply click on the Start profiling button to initiate this process.

Collect basic statistics and profile data with default profiling checks

Automatically activated checks

Once new tables are imported, DQOps automatically activates profiling and monitoring checks which are which are pre-enabled by data quality policies. These checks detect volume anomalies, data freshness anomalies, empty tables, table availability, schema changes, anomalies in the count of distinct values, and null percent anomalies. The profiling checks are scheduled to run at 12:00 p.m. on the 1st day of every month, and the monitoring checks are scheduled to run daily at 12:00 p.m.

Profiling checks are designed to assess the initial data quality score of a data source. Profiling checks are also useful for exploring and experimenting with various types of checks and determining the most suitable ones for regular data quality monitoring.

Monitoring checks are standard checks that monitor the data quality of a table or column. They can also be referred to as Data Observability checks. These checks capture a single data quality result for the entire table or column.

Add a Teradata connection using DQOps Shell

To add a connection run the following command in DQOps Shell.

dqo> connection add

Fill in the data you will be asked for.

Connection name (--name): connection1
Database provider type (--provider):
 [ 1] bigquery
 [ 2] clickhouse
 [ 3] databricks
 [ 4] db2
 [ 5] duckdb
 [ 6] hana
 [ 7] mariadb
 [ 8] mysql
 [ 9] oracle
 [10] postgresql
 [11] presto
 [12] questdb
 [13] redshift
 [14] snowflake
 [15] spark
 [16] sqlserver
 [17] teradata
 [18] trino
Please enter one of the [] values: 17
Teradata host name (--teradata-host) [${TERADATA_HOST}]: localhost
Teradata port number (--teradata-port) [${TERADATA_PORT}]: 1025
Teradata user name (--teradata-user) [${TERADATA_USER}]: test
Teradata user password (--teradata-password) [${TERADATA_PASSWORD}]: xxx
Connection connection1 was successfully added.
Run 'table import -c=connection1' to import tables.

You can also run the command with parameters to add a connection in just a single step.

dqo> connection add --name=connection1
--provider=teradata
--teradata-host=localhost
--teradata-port=1025
--teradata-user=test
--teradata-password=xxx

After adding connection run table import -c=connection1 to select schemas and import tables.

DQOps will ask you to select the schema from which the tables will be imported.

You can also add the schema and table name as parameters to import tables in just a single step.

dqo> table import --connection={connection name}
--schema={schema name}
--table={table name}

DQOps supports the use of the asterisk character * as a wildcard when selecting schemas and tables, which can substitute any number of characters. For example, use pub* to find all schema a name with a name starting with "pub". The * character can be used at the beginning, middle, or end of the name.

Connections configuration files

Connection configurations are stored in the YAML files in the ./sources folder. The name of the connection is also the name of the folder where the configuration file is stored.

Below is a sample YAML file showing an example configuration of the Teradata data source connection.

apiVersion: dqo/v1
kind: source
spec:
  provider_type: teradata
  teradata:
    host: localhost
    port: 1025
    user: test
    password: xxx
  incident_grouping:
    grouping_level: table_dimension_category
    minimum_severity: warning
    max_incident_length_days: 60
    mute_for_days: 60

Reference of all connection parameters

Complete documentation of all connection parameters used in the spec.teradata node is described in the reference section of the TeradataParametersSpec YAML file format.

Next steps

  • We have provided a variety of use cases that use openly available datasets from Google Cloud to help you in using DQOps effectively. You can find the complete list of use cases here.
  • DQOps allows you to keep track of the issues that arise during data quality monitoring and send alert notifications directly to Slack. Learn more about incidents and notifications.
  • The data in the table often comes from different data sources and vendors or is loaded by different data pipelines. Learn how data grouping in DQOps can help you calculate separate data quality KPI scores for different groups of rows.