DatriseAI-first ETL

Teradata to ClickHouse Integration

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

How Datrise loads Teradata into ClickHouse

Datrise syncs Teradata's tables, rows, schemas, indexes, primary indexes, and query history into ClickHouse as a MergeTree table per source entity. Flexible or custom fields land in JSON or Map columns, and timestamps such as created, updated, and status changes are typed as DateTime64.

Sync is incremental: Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge, so re-runs update only what changed. Partition by month and order by (entity id, updated-at) for fast range scans. ClickHouse deduplicates asynchronously on merge, so Datrise uses ReplacingMergeTree and FINAL-safe queries rather than assuming immediate upserts.

Ideal for high-volume event analytics that need sub-second aggregation.

Endpoints

Teradata: Teradata analytical database for enterprise workloads.

ClickHouse: Columnar OLAP engine for fast aggregations.

How Teradata entities map to ClickHouse

Teradata entityClickHouse objectNotes
tablesteradata_d_tablesid PK · custom fields → JSON or Map columns
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 ClickHouse?

Flexible values are stored as JSON or Map columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native ClickHouse types.

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

It runs incrementally — Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge.

Related pipelines

Early access

Connect Teradata to ClickHouse 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.