Teradata

This article describes the integration with the Teradata connector, enabling streamlined metadata management through crawling, profiling, data preview, and lineage building (Auto and Manual). It ensures secure authentication via Credential Manager.

Overview

Connector Details

Connector Category

Data Warehouse

Connectivity

[How the connection is established with Teradata]

JDBC

Connector Features

Feature
Availability

Crawling

Delta Crawling

Profiling

Query Sheet

Data Preview

Auto Lineage

Manual Lineage

Secure Authentication via Credential Manager

Data Quality

DAM (Data Access Management)

Bridge

Metadata Mapping

The following objects are crawled from the Teradata and mapped to the corresponding UI assets.

Teradata Object
Teradata Attribute
OvalEdge Attribute
OvalEdge Category
OvalEdge Type

Schema

Schema name

Schema

Databases

Schema

Schema

Schema comment

Source Description

Databases

Schema

Table

Tablename

Table

Tables

Table

Table

Table_Type

Type

Tables

Table

Table

Tablecomment

Source Description

Descriptions

Source Description

Columns

Column_Name

Column

Table Columns

Columns

Columns

Data_Type

Column Type

Table Columns

Columns

Columns

Comments

Source Description

Table Columns

Columns

Columns

Data_Length

Data Type Size

Table Columns

Columns

View

View Name

View

Tables

View

View

Text

View Query

Views

View

Procedures

Name

Name

Procedures

Procedures

Procedures

Text

Procedure Query

-

Procedures

Set up a Connection

Prerequisites

The prerequisites to establish a connection:

Whitelisting Ports

Whitelist the inbound port to allow OvalEdge to connect to the Teradata Server database.

Service Account User Permissions

👨‍💻 Who can provide these permissions? The Teradata administrator grants these permissions, as standard accounts may not have the required access to assign them independently.

Objects
System Tables
Permissions

Schema

DBC

Select

Tables

DBC.All_RI_ChildrenV

Select/Read

Tables

DBC.TablesV

Select/Read

Tables

DBC.IndicesV

Select/Read

Tables

DBC.ColumnsV

Select/Read

Tables

DBC.FunctionsV

Select/Read

Connection Configuration Steps

  1. Log in to OvalEdge, go to Administration > Connectors, click + (New Connector), search for Teradata, and complete the required parameters.

Fields marked with an asterisk (*) are mandatory for establishing a connection.

Field Name
Description

Connector Type

By default, "Teradata" is displayed as the selected connector type.

Credential Manager*

Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on the selection.

Supported Credential Managers:

  • Database

  • HashiCorp

  • AWS Secrets Manager

  • Azure Key Vault

License Add-On

Auto Lineage

Supported

Data Quality

Not Supported

Data Access

Not Supported

  • Select the Auto Lineage Add-On checkbox to build data lineage automatically.

Connector Name*

Enter a unique name for the Teradata connection

(Example: "Teradata_Prod").

Connector Environment

Select the environment (Example: PROD, STG) configured for the connector.

Connector Description

Enter the description related to the connector.

Server*

Enter the IP address of the server where Teradata is hosted.

Port*

Enter the required Teradata port number.

Database*

The ‘Database’ field specifies the default schema to connect to within the Teradata server.

Example: If the target database is sales_db, enter sales_db to connect directly instead of the default schema.

Driver*

By default, Teradata uses ‘com.teradata.jdbc.TeraDriver.’ This field is not editable.

Username*

Enter the Username for the Teradata server.

Password*

Enter the Password associated with the Teradata Username.

Connection String

Configure the connection string for the Teradata server:

  • Automatic Mode: The system generates a connection string based on the provided credentials.

  • Manual Mode: Enter a valid connection string manually.

Replace placeholders with actual server details:

  • {server} refers to the Teradata host or IP address.

  • {sid} refers to the database name (schema).

Authentication Plugins: jdbc:teradata://{server}/DBS_PORT={port},database={sid}

This is the default authentication string used for connecting to the Teradata database.

Plugin Server

Enter the server name when running as a plugin server.

Plugin Port

Enter the port number on which the plugin is running.

Default Governance Roles

Default Governance Roles*

Select the appropriate users or teams for each governance role from the drop-down list. All users and teams configured in OvalEdge Security are displayed for selection.

Admin Roles

Admin Roles*

Select one or more users from the dropdown list for Integration Admin and Security & Governance Admin. All users configured in OvalEdge Security are available for selection.

No of Archive Objects

No Of Archive Objects*

This shows the number of recent metadata changes to a dataset at the source. By default, it is off. To enable it, toggle the Archive button and specify the number of objects to archive.

Example: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.

Bridge

Select Bridge*

If applicable, select the bridge from the drop-down list.

The drop-down list displays all active bridges configured in OvalEdge. These bridges enable communication between data sources and OvalEdge without altering firewall rules.

  1. After entering all connection details, the following actions can be performed:

    • Click Validate to verify the connection.

    • Click Save to store the connection for future use.

    • Click Save & Configure to apply additional settings before saving.

  2. The saved connection will appear on the Connectors home page.

Manage Connector Operations

Crawl/Profile

To perform crawl and profile operations, users must be assigned the Integration Admin role.

The Crawl/Profile button allows users to select one or more schemas for crawling and profiling.

  1. Navigate to the Connectors page and click Crawl/Profile.

  2. Select the schemas to crawl.

  3. The Crawl option is selected by default. Click the Crawl & Profile radio button to enable both operations.

  4. Click Run to collect metadata from the connected source and load it into the Data Catalog.

  5. After a successful crawl, the information appears in the Data Catalog > Databases tab.

The Schedule checkbox allows automated crawling and profiling at defined intervals, from a minute to a year.

  1. Click the Schedule checkbox to enable the Select Period drop-down.

  2. Select a time period for the operation from the drop-down menu.

  3. Click Schedule to initiate metadata collection from the connected source.

  4. The system will automatically execute the selected operation (Crawl or Crawl & Profile) at the scheduled time.

Other Operations

The Connectors page in OvalEdge provides a centralized view of all configured connectors, including their health status.

Managing connectors includes:

  • Connectors Health: Displays the current status of each connector, with a green icon for active connections and a red icon for inactive connections, helping monitor connectivity to data sources.

  • Viewing: Click the Eye icon next to the connector name to view connector details, including Tables, Views, and Columns.

Nine Dots Menu Options:

To view, edit, validate, configure, build lineage, or delete connectors, click on the Nine Dots menu.

  • Edit Connector: Update and revalidate the data source.

  • Validate Connector: Check the integrity of the connection.

  • Settings: Modify connector settings.

    • Crawler: Configure data extraction.

    • Profiler: Customize data profiling rules and methods.

    • Query Policies: Define query execution rules based on roles.

    • Access Instructions: Add notes on how data can be accessed.

    • Business Glossary Settings: Manage term associations at the connector level.

    • Connection Pooling: Allows configuring parameters such as maximum pool size, idle time, and timeouts directly within the application.

    • Others: Configure notification recipients for metadata changes.

  • Build Lineage: Automatically build data lineage using source code parsing.

  • Delete Connector: Remove a connector with confirmation.


Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA.

Last updated

Was this helpful?