Teradata D → Sisense
AI-first ETL from Teradata D into Sisense. Governed entities, incremental sync, typed landing tables.
How Datrise loads Teradata D into Sisense
Datrise syncs Teradata D's records, events, and configuration objects into Sisense as modeled tables for a Sisense ElastiCube (or live connection). Flexible or custom fields land in flattened columns for the cube, and timestamps such as created, updated, and status changes are typed as date/time fields.
Sync is incremental: Datrise uses incremental ElastiCube builds on changed rows, so re-runs update only what changed. Date-partitioned facts to speed cube builds. ElastiCube is an in-memory model, so Datrise lands incremental, build-friendly tables rather than forcing full rebuilds.
Ideal for embedded analytics on an in-memory engine.
Endpoints
Teradata D: SaaS or API data source for analytics and warehouse sync.
Sisense: Analytics platform with elastic data models and embedded analytics.
How Teradata D entities map to Sisense
| Teradata D entity | Sisense object | Notes |
|---|---|---|
| records | teradata_d_records | id PK · custom fields → flattened columns for the cube |
| events | teradata_d_events | date/time fields events |
| configuration objects | teradata_d_configuration_objects | id PK · linked to teradata_d_records |
FAQ
How does Datrise handle Teradata D's custom fields in Sisense?
Flexible values are stored as flattened columns for the cube, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Sisense types.
How does the Teradata D to Sisense sync stay up to date?
It runs incrementally — Datrise uses incremental ElastiCube builds on changed rows.
Related pipelines
More destinations for Teradata D
Early access
Connect Teradata D to Sisense 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.