Teradata

Adding and configuring a Teradata connection within Qualytics empowers the platform to build a symbolic link with your schema to perform operations like data discovery, visualization, reporting, syncing, profiling, scanning, anomaly surveillance, and more.

This documentation provides a step-by-step guide on adding Teradata as a source datastore in Qualytics. It covers the entire process from initial connection setup to testing and finalizing the configuration.

By following these instructions, enterprises can ensure their Teradata environment is properly connected with Qualytics, unlocking the platform's potential to help you proactively manage your full data quality lifecycle.

Let’s get started 🚀

Teradata Setup Guide

Qualytics connects to Teradata through the Teradata JDBC driver. It uses JDBC metadata APIs to discover databases, tables, columns, and primary keys. Qualytics automatically filters out Teradata system databases (DBC, SYSLIB, SYSSPATIAL, SYSUDTLIB, SystemFe, TDQCD, TDStats, TDPUSER, SYSUIF, All, Crashdumps, EXTUSER, LockLogShredder, SQLJ, SYSADMIN, SYSBAR, SYSJDBC) during schema discovery.

Minimum Teradata Permissions (Source Datastore)

Example: Source Datastore User (Read-Only)

Replace <database_name> and <password> with your actual values.

-- Create a dedicated read-only user
CREATE USER qualytics_read AS
  PASSWORD = '<password>'
  PERM = 0
  SPOOL = 1000000000;

-- Grant logon access
GRANT LOGON ON ALL TO qualytics_read;

-- Grant read access to the target database
GRANT SELECT ON <database_name> TO qualytics_read;
GRANT SHOW ON <database_name> TO qualytics_read;

Troubleshooting Common Errors

Detailed Troubleshooting Notes

Authentication Errors

The error Authentication failed indicates that the credentials are incorrect.

Common causes:

• Incorrect password: the password does not match the one set for the user.
• User does not exist: the username was misspelled or does not exist in the Teradata system.
• LDAP authentication: if LDAP is enabled, the credentials must match the LDAP directory, not the Teradata internal user store.

Permission Errors

The error User does not have SELECT access means the user authenticated successfully but lacks the necessary grants on the target database.

Common causes:

• Missing SELECT on database: the user does not have SELECT on the target database or specific tables.
• Missing SHOW on database: the user cannot view object definitions needed for metadata discovery.
• Access to system databases: the user is trying to access a filtered system database (e.g., DBC, SYSLIB).

Connection Errors

The error Connection refused means the Teradata server is not reachable from the Qualytics server.

Common causes:

• Firewall: a firewall is blocking connections on the Teradata port (default 1025).
• Server not running: the Teradata server is not started or is in a maintenance state.
• Wrong host: the hostname or IP address in the connection form is incorrect.

Add a Source Datastore

A source datastore is a storage location Qualytics connects to so it can profile, scan, and monitor data. Adding Teradata as a source lets Qualytics query it through the Teradata JDBC driver and run quality operations on the tables it discovers.

Before you start, review the Minimum Teradata Permissions the connecting user needs.

Field reference

The Add Datastore page shows the sections below when Teradata is selected. When reusing an existing connection, the Connection Properties and Secrets Management sections come already filled in and read-only: Qualytics has already validated those credentials, so you fill in only the Datastores Extraction and the Datastore Properties. To change a saved connection's credentials, edit the connection through the Manage Connections page; edits there apply to every datastore that reuses the connection.

Connection Properties

These fields define the Teradata system Qualytics connects to and the account it connects with. They belong to the connection: when reusing an existing connection, they come already filled in and read-only.

Secrets Management

This group is optional: use it only if you want Qualytics to pull credentials from a secrets manager instead of typing them into the form. Turn on HashiCorp Vault to show the fields below. Despite the label, any secrets manager that exposes a compatible REST API works, not only HashiCorp Vault; see Secrets Management. It also belongs to the connection: read-only when reusing an existing connection.

Datastores Extraction

Pick the database Qualytics should read from, and choose whether the connection is encrypted. You fill these in on both flows.

Datastore Properties

Common fields for every source datastore, shown below the Datastores Extraction section. You fill these in on both flows.

Steps

There are two ways to set up the connection: reuse a connection you already saved (Existing Connection) or create a new one from scratch (New Connection). The tabs below walk through each option; pick the one you want to follow. Each field is described in the Field reference above.

API Payload Examples

Creating a Source Datastore

This section provides a sample payload for creating a datastore. Replace the placeholder values with actual data relevant to your setup.

Endpoint (Post): /api/datastores (post)

{
    "name": "your_datastore_name",
    "teams": ["Public"],
    "schema": "schema_name",
    "enrichment_only": false,
    "trigger_sync": true,
    "connection": {
        "name": "your_connection_name",
        "host": "teradata_host",
        "port": 1025,
        "username": "teradata_user",
        "password": "teradata_password",
        "type": "teradata"
        }
}

{
    "name": "your_datastore_name",
    "teams": ["Public"],
    "schema": "schema_name",
    "enrichment_only": false,
    "trigger_sync": true,
    "connection_id": 123
}

# Step 1: Create a Connection
qualytics connections create \
    --type teradata \
    --name "your_connection_name" \
    --host ${TERADATA_HOST} \
    --port 1025 \
    --username ${TERADATA_USER} \
    --password ${TERADATA_PASSWORD}

# Step 2: Create a Source Datastore
qualytics datastores create \
    --name "your_datastore_name" \
    --connection-name "your_connection_name" \
    --schema dbc

"connection": {
    "name": "your_connection_name",
    "host": "teradata_host",
    "port": 1025,
    "username": "teradata_user",
    "password": "teradata_password",
    "type": "teradata",
    "parameters": {
        "ssl": "false"
    }
}

Link an Enrichment Datastore to a Source Datastore

Endpoint Patch:

/api/datastores/{datastore-id}/enrichment/{enrichment-id} (patch)