Data Warehouse connector

The Teradata data catalog your whole team can trust.

The Dawiso Teradata connector turns Vantage into a searchable data catalog: every database, table, view, function and index, with lineage to BI downstream.

Read the docs

Live connector Stable connector

Teradata

Dawiso

Metadata-only · your data never leaves the source

Type: Enterprise data warehouse
Auth: User + password (read-only)
Sync: Scheduled, incremental
Direction: Read-only · metadata

First things first

What is a data connector?

Metadata-only Read-only access Incremental sync Cross-system lineage

A data connector is the bridge between a tool in your stack and the catalog that gives you a unified view of it. Once a connector is configured, it reaches into the source system on a schedule, reads out the metadata - schemas, tables, dashboards, jobs, ownership, lineage - and represents it inside the catalog. Your actual rows and values stay where they are.

Connectors are the reason a data catalog can answer questions like "which Power BI dashboard depends on this Snowflake table?" or "who owns the orders topic in Kafka?" - automatically, without anyone keeping a spreadsheet up to date.

Three properties separate a good connector from a brittle one: it should be read-only and safe, it should be incremental so a full re-scan isn't required for every refresh, and it should resolve lineage across system boundaries, not just inside one tool.

About the platform

What is Teradata?

Teradata is the long-running enterprise data warehouse, founded in 1979. Banks, telcos, retailers and airlines use it as their analytical home base: customer 360, billing, churn, regulatory reporting. The current platform is Vantage, available on-premises, as VantageCloud Lake on AWS / Azure / Google Cloud, and as a managed service.

Teradata's own DBC views (DatabasesV, TablesV, ColumnsV) cover what's inside Vantage. What they don't cover is the Cognos or Power BI report consuming the table, the data product the business owns, and the policy security signed off on. That's where the Dawiso Teradata data catalog joins the picture: read-only, metadata-only, and cross-platform.

Architecture

How Dawiso connects to Teradata

A small read-only role on the Teradata side. The Dawiso scanner pulls metadata on a schedule. Everything ends up in your catalog, business-readable.

Source

Teradata Vantage

Databases
Tables & views
Functions & procedures
Indexes & constraints

REST · JDBC

Dawiso scanner

Read-only metadata

Schema & object discovery
Dependency resolution
SQL flow parsing (optional)
Sampling on opt-in

Internal

Catalog

Dawiso platform

Searchable metadata
Lineage & ownership
Business glossary
Policy & classifications

Connection details

Protocol: Teradata JDBC + DBC.* catalog views
Authentication: Teradata user + password · read-only grants
Lineage: Object dependencies resolved from DBC catalog views; object-level lineage built from parsed view and procedure SQL via Data Flow parsing on enterprise plans

Setup

Connect Teradata in 4 steps

01

Create a Dawiso user

CREATE USER "dawiso_user" FROM [parent_database] AS PASSWORD = "<password>" using a Teradata account with administrator-level privileges.
02

Grant catalog access

GRANT SELECT on DBC.DatabasesV, TablesV, ColumnsV, IndicesV, FunctionsV and All_RI_ChildrenV. Read-only against system catalog views.
03

Connect in Dawiso

Add the Teradata host (DNS, IP or qualified name like mycompany.teradata.com), port 1025, plus user and password. Choose Shared or Private connection.
04

Run ingestion

Provide a comma-separated list of databases to ingest. Scheduled incremental sync keeps the catalog current. Flow parsing resolves object-level lineage on enterprise plans.

Capabilities

What you get with the Teradata connector

Database & table catalog

Every Teradata database, table, view, function and procedure is searchable, with column descriptions, data types, owners and the indexes behind them.
Object-level lineage

Cross-platform lineage from a Cognos or Power BI report through Teradata views and stored procedures down to the source table that feeds them, via Data Flow parsing on enterprise plans.
PII classification

Classify a column once. Dawiso flags every Teradata column carrying birth number, IBAN or government IDs across all databases in scope.
Ownership & certification

Mark Teradata tables as certified, deprecated or under review. Owner, steward and SLA are visible directly in the catalog.
Referential constraints

Parent and child relationships from DBC.All_RI_ChildrenV are imported, so join paths and foreign-key chains are part of the catalog and lineage.
GDPR & DORA evidence

Sensitive columns are tagged and the policy follows them through views and into downstream BI, with a full audit trail for regulators.

Business value

Why teams turn on the Teradata connector

-65%
Fewer 'which table?' pings

Analysts find the certified Teradata table in Dawiso instead of pinging the DBA to ask which view the customer-360 report actually reads from.
10x
Faster impact analysis

Before altering a Teradata view, see exactly which BI reports and downstream tables depend on it. Seconds, not days.
Read-only
Zero risk to production

Dawiso uses a dedicated user with SELECT on DBC views only. Your Teradata data, your queries and your write paths are untouched.

Ready to catalog your Teradata?

Set up the connector in an afternoon. See your first lineage graph the same day.

Read the docs

Frequently asked questions

Still curious? Talk to our team ->

What is a data catalog in a database?

A database's catalog (data dictionary) describes its tables, columns and relationships. For Teradata, Dawiso reads the DBC dictionary views read-only and turns them into a business-readable catalog with lineage, ownership and search.

What is metadata in Teradata?

Teradata stores metadata in DBC dictionary tables describing databases, tables, columns and access rights. Dawiso reads them read-only and builds a searchable catalog with classification and cross-platform lineage.

What is a data catalog used for?

A data catalog makes every Teradata table discoverable, documented and trustworthy. Dawiso turns dictionary metadata into one searchable catalog the whole business can use.

What permissions does Dawiso need in Teradata?

A dedicated user (e.g. dawiso_user) with SELECT on DBC.DatabasesV, TablesV, ColumnsV, IndicesV, FunctionsV and All_RI_ChildrenV. The Teradata account creating the user needs administrator-level privileges. Read-only end to end; Dawiso does not modify your data.

Does it work with VantageCloud and on-prem Teradata?

Yes. The connector uses the standard Teradata JDBC driver on port 1025 against DBC catalog views, which are the same across on-prem Teradata, VantageCloud Lake and VantageCloud Enterprise.

Does Dawiso copy our Teradata data?

No. Dawiso queries DBC.* catalog views for metadata only. Row-level data stays inside Teradata. Column profiling and sampling are opt-in per data source and never run automatically.

How is lineage built?

Object dependencies come from DBC views including All_RI_ChildrenV. For object-level resolution, Dawiso parses SQL from view and stored-procedure definitions via Data Flow parsing. Teradata is one of the supported targets for this enterprise feature.