Data Warehouse


Connectivity Summary

An out-of-the-box connector is available for Teradata databases to support crawling database objects, profiling sample data, and lineage building.

The connectivity to Teradata is via the JDBC driver, which is included in the platform.
The following Teradata versions supported by the connector are mentioned below: 

Edition: no-awssdk
Version: 1.0x

The drivers used by the connector are mentioned below:

Driver/API: Teradata JDBC driver
Version: 1.0
Details: Is JDBC 1.0
Note: Latest version is 2.0

Technical Specifications

The following are the connector capabilities mentioned below:


Feature Supported Objects Remarks
Crawling Tables  
Table columns

Supported Data Types:


Stored procedures  
Usage Statistics  



See this article Profile Data to know more about Profiling.

Feature Support Remarks
Table Profiling Row count, Columns count, View sample data  
View Profiling Row count, Columns count, View sample data The view is treated as a table for profiling purposes
Column Profiling Min, Max, Null count, distinct, top 50 values  
Full Profiling Supported  
Sample Profiling Supported  

 Lineage Building

Lineage Entities Details
Table lineage Supported
Column lineage Supported
Lineage Sources Stored procedures, functions, views, query logs


Operation Details
Select Supported
Insert Not supported, by default.
Update Not supported, by default.
Delete Not supported, by default.
Joins within database Supported
Joins outside database Not supported
Aggregations Supported
Group By Supported
Order By Supported

By default, the service account provided for the connector will be used for any query operations. If the service account has write privileges, then Insert / Update / Delete queries can be executed.


To use the connector, the following need to be available:

  • Connection details as specified in the following section should be available.
  • An admin/service account with read privileges.
  • JDBC driver is provided by default. In case it needs to be changed, add Teradata client drivers into the OvalEdge Jar path to communicate to the Teradata database. 

Connection Details

The following are the connection settings that need to be added for connecting to a Teradata database:


  • Database Type: Teradata
  • License Type: Standard 
  • Connection Name: Select a Connection name for the Teradata database. The name that you specify is a reference name to easily identify your Teradata database connection in OvalEdge. Example: Teradata Connection1
  • Hostname / IP Address: Database instance URL (on-premises/cloud-based)
  • Port number: 1025
  • Sid/Database: Name of the database to connect.
  • Username: User account login credential (only for Teradata Authentication)
  • Password: Password (only for Teradata Authentication)
  • Driver Name: JDBC driver name for Teradata. It will be auto-populated.
    Example: TeradataJDBC42-no-awssdk-
  • Connection String: Teradata connection string. Set the Connection string toggle button to automatic, to get the details automatically from the credentials provided. Alternatively, you can manually enter the string.

    Example: jdbc:Teradata://;database=customers

Once connectivity is established, additional configurations for Crawling and Profiling can be specified.

Property  Details
Crawler configurations
Tables, views & columns By default, it is selected true
Relationships Need to select for crawl relationships
Crawler rules Default includes tables regex has  regex = (.*), which can crawl all the tables
Profile Settings
Tables and columns By default, it is selected true
Views and columns By default, it is selected true
Profile Rules Default includes tables regex has  regex = (.*), which can profile all the tables