Teradata

Crawling

Tables

-

Crawling

Table Columns

-

Crawling

Views

-

Crawling

Stored Procedures

-

Crawling

Functions

-

Features

Details

Remarks

Table Profiling

Row count, Columns count, View sample data

Not Supported Data Types: 

• JSON
• Clob
• Blob

View Profiling

Row count, Columns count, View sample data

-

Column Profiling

Min, Max, Null count, distinct, top 50 values

-

Full Profiling 

Supported

-

Sample Profiling

Supported

-

Lineage Entities

Details

Table lineage

Supported

Column lineage

Supported

Lineage Sources

Stored Procedures, Functions, and Views

Operation

Details

Select

Supported

Insert

Supported, provided its service account has the permission

Update

Supported, provided its service account has the permission

Delete

Supported, provided its service account has the permission

Joins within database

Supported

Joins outside database

Not supported

Aggregations

Supported

Group By

Supported

Order By

Supported

Driver

Version

Details

JDBC Driver

19.3.0.0

Is JDBC 1.0 

https://s3.amazonaws.com/Teradata-downloads/drivers/jdbc/1.2.41.1065/TeradataJDBC42-no-awssdk-1.2.41.1065.jar

Note: The latest version is 2.0

Connection Validation

Read

Crawl Schemas, Tables

Read

Profile Schemas, Tables

Read, Select

Field Name

Description

Connector Type

This field allows users to select the connector from the drop-down list provided. By default, 'Teradata' is displayed as the selected connector type.

Credential Manager*

Select the option from the drop-down menu where users want to save their credentials:

OE Credential Manager: The Teradata connection is configured with the basic Username and Password of the service account in real-time when OvalEdge establishes a connection to the Teradata database. Users must manually add the credentials if the OE Credential Manager option is selected.

HashiCorp: The credentials are stored in the HashiCorp database server and fetched from HashiCorp to OvalEdge.  

AWS Secrets Manager: The credentials are stored in the AWS Secrets Manager database server and fetched from the AWS Secrets Manager to OvalEdge.

For more information on Azure Key Vault, refer to Azure Key Vault.

For more information on Credential Manager, refer to Credential Manager.

License Add Ons

All the connectors will have a Base Connector License by default, which allows users to crawl and profile to obtain metadata and statistical information from a data source. 

OvalEdge supports various License Add-Ons based on the connector’s functionality requirements.

• Select the Auto Lineage Add-On license that enables the automatic construction of the Lineage of data objects for a connector with the Lineage feature. 
• Select the Data Quality Add-On license to identify, report, and resolve the data quality issues for a connector whose data supports data quality using DQ Rules/functions, Anomaly detection, Reports, and more.

Connector Name*

The connection name refers to the Teradata database connection in the OvalEdge application.

Connector Environment

The Connector Environment drop-down list allows users to select the environment configured for the connector from the drop-down list. 

For example, select PROD or STG (based on the items configured in the OvalEdge configuration for the connector environment).

The purpose of the environment field is to help users identify which connector is connecting to what type of system environment (Production, STG, or QA).

Note: The Configuring Environment Variables section explains setting up environment variables.

Server*

Specify the name of the Teradata database instance server URL, which is accessible by the OvalEdge application. 

Format: <account>.teradatacomputing.com

Port Number*

Port number 1025 is the default port Teradata uses when connecting to a server over the internet.

Database*

Provide the name of the database that is associated with the Teradata connection, if necessary. It is a user-specified database name to crawl the metadata of selected connectors.

Driver*

A JDBC driver is a Java library file with the extension .jar that connects to a database. The driver details associated with the Teradata database will be auto-populated by default.

Example: com.teradata.jdbc.TeraDriver

Username*

Enter the Service Account Username for the Teradata Server name.

Password*

Enter the password for the Teradata Server name.

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.

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

Plugin Server

Enter the server name if you are running this as a plugin.

Plugin Port

The port number on which the plugin is running.

Default Governance Roles

Steward*

Select the Steward from the drop-down list options.

Custodian*

Select the Custodian from the drop-down list options.

Owner*

Select the Owner from the drop-down list options.

Governance Roles 4, 5, 6*

Select the respective user from the drop-down options.

Note: The drop-down list displays all the configurable roles (single user or a team) as per the configurations made in the OvalEdge Security > Governance Roles section.

Admin Roles

Integration Admins*

To add Integration Admin Roles, search for or select one or more roles from the Integration Admin options, then click the Apply button.
The Integration Admin's responsibilities include configuring crawling and profiling settings for the connector and deleting connectors, schemas, or data objects.

Security and Governance Admins*

To add Security and Governance Admin roles, search for or select one or more roles from the list and then click the Apply button.
The Security and Governance Admin is responsible for:

• Configuring role permissions for the connector and its associated data objects.
• Adding admins to set permissions for the connector's roles and associated data objects.
• Updating governance roles.
• Creating custom fields.
• Developing Service Request templates for the connector.
• Creating approval workflows for  Service Request templates.

No. of Archive Objects*

The number of archive objects indicates the number of recent metadata modifications made to a dataset at a remote/source location. By default, the archive objects feature is deactivated. However, users may enable it by clicking the Archive toggle button and specifying the number of objects they wish to archive. 

Select Bridge*

With the OvalEdge Bridge component, any cloud-hosted server can connect with any on-premise or public cloud data source(s) without modifying firewall rules. A bridge provides real-time control, making data movement between source and destination easy. For more information, refer to

Bridge Overview.

S.No

Error Message(s)

Description

1

Failed to establish a connection. Please check the credentials.

Invalid credentials are provided or the user or role does not have access.

2

Connection Timeout

Invalid credentials are provided or the server is not running.

Connection Settings

Description

Crawler

Crawler settings are configured to connect to a data source and collect and catalog all the data elements in metadata.

Profiler

Profiler settings govern gathering statistics and informative summaries about the connected data source(s). These statistics can help assess the quality of data sources before using them for analysis. Profiling is always optional; crawling can be run without profiling. 

Query Policies

A query policy enforces security by preventing users with specific roles from performing certain query functions on the data source.

Access Instruction

Access Instruction allows the data owner to instruct others on using the objects in the application.

Business Glossary Settings

The Business Glossary Settings provide flexibility and control over how users view and manage term association within a business glossary at the connector level.

Others

The Enable/Disable Metadata Change Notifications option sets the change notification about metadata changes of the data objects.

• Users can use the toggle button to set the Default Governance Roles (Steward, Owner Custodian, etc.) 
• Using the Roles and Teams, users can select the role and team to receive the notification of metadata changes.