DatriseAI-first ETL

Teradata to Holistics Integration

AI-first ETL from Teradata into Holistics. Governed entities, incremental sync, typed landing tables.

How Datrise loads Teradata into Holistics

Datrise syncs Teradata's tables, rows, schemas, indexes, primary indexes, and query history into Holistics as warehouse tables modeled in Holistics. Flexible or custom fields land in flattened columns for the modeling layer, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the modeled tables, so re-runs update only what changed. Date-partitioned facts for fast aggregates. Holistics models data as code on top of SQL, so Datrise lands stable column names to keep your models from drifting.

Ideal for as-code BI modeling on a warehouse.

Endpoints

Teradata: Teradata analytical database for enterprise workloads.

Holistics: Self-service BI with modeling layers and scheduled report delivery.

How Teradata entities map to Holistics

Teradata entityHolistics objectNotes
tablesteradata_d_tablesid PK · custom fields → flattened columns for the modeling layer
rowsteradata_d_rowsid PK · linked to teradata_d_tables
schemasteradata_d_schemasid PK · linked to teradata_d_tables
indexesteradata_d_indexesid PK · linked to teradata_d_tables

FAQ

How does Datrise handle Teradata's custom fields in Holistics?

Flexible values are stored as flattened columns for the modeling layer, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Holistics types.

How does the Teradata to Holistics sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the modeled tables.

Related pipelines

Early access

Connect Teradata to Holistics the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.