Teradata

Supported Data warehouses & lakehouses

Catalog Teradata Vantage databases, tables, views, columns, macros and procedures from the DBC data dictionary.

Capabilities

CapabilitySupportNotes
Tables, views & columns Supported Read from DBC.TablesV and DBC.ColumnsV.
Keys, constraints & indexes Partial
Procedures & functions Supported
Data lineage Supported
Lineage from query history Partial Statements can be extracted from DBQL (DBC.QryLogSQLV) when query logging is enabled.
Business glossary links Supported
Data quality probes Supported
Data profiling Supported
Data classification Supported
Chat with your data Supported

Connection settings

Create the connection on the Blindata Agent from Settings > Agents > Connections with the connection wizard, choosing Teradata in the technology step.

Driver classcom.teradata.jdbc.TeraDriver
JDBC URLjdbc:teradata://localhost/DATABASE=mydb
Authentication
Service principal (shared technical user)
User principal (personal credentials, BYOC)
Ephemeral credentials (asked at each run)
Crawling strategySQL

The Blindata Agent does not include this driver: download the vendor JDBC driver and copy the .jar into the agent drivers folder, as described in Add JDBC drivers. Driver properties can be added under Advanced settings in the connection wizard.

Prerequisites & permissions

  • A Blindata Agent installed with network access to Teradata.
  • The vendor JDBC driver installed on the agent (see Add JDBC drivers).
  • SELECT on the DBC views (DBC.TablesV, DBC.ColumnsV, DBC.IndicesV).
  • SELECT on DBC.QryLogSQLV for query history.

Set up metadata crawling

  1. Create the connection to Teradata on the agent (see Connection settings) and use Test to verify it.
  2. Create or open the system that represents Teradata in the catalog and link it to the connection.
  3. In the CRAWLING tab add a crawling job with strategy SQL.
  4. Run a TEST to check the number of extracted objects, then RUN or schedule the job.

The job options and the column aliases of every extraction query are described in the Generic JDBC reference.

Updated on 16 Oct 2026