DatriseAI-first ETL

Teradata to Spotfire Integration

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

How Datrise loads Teradata into Spotfire

Datrise syncs Teradata's tables, rows, schemas, indexes, primary indexes, and query history into Spotfire as warehouse tables or in-memory data for Spotfire analyses. Flexible or custom fields land in flattened columns for visualizations, and timestamps such as created, updated, and status changes are typed as date/time columns.

Sync is incremental: Datrise uses incremental refresh of the connected tables or in-memory data, so re-runs update only what changed. Date-partitioned facts. Spotfire can load data in-memory, so Datrise keeps the backing tables incremental so analyses refresh without full reloads.

Ideal for interactive analytical visualization and data science.

Endpoints

Teradata: Teradata analytical database for enterprise workloads.

Spotfire: Visual analytics platform for interactive dashboards and data science workflows.

How Teradata entities map to Spotfire

Teradata entitySpotfire objectNotes
tablesteradata_d_tablesid PK · custom fields → flattened columns for visualizations
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 Spotfire?

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

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

It runs incrementally — Datrise uses incremental refresh of the connected tables or in-memory data.

Related pipelines

Early access

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