DatriseAI-first ETL

IBM IBM Db2 to GoodData Integration

AI-first ETL from IBM IBM Db2 into GoodData. Governed entities, incremental sync, typed landing tables.

How Datrise loads IBM IBM Db2 into GoodData

Datrise syncs IBM IBM Db2's tables, rows, schemas, indexes, primary keys, and change data into GoodData as warehouse tables GoodData maps into its logical data model. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date dimensions.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. GoodData's LDM maps datasets by keys, so Datrise lands stable primary and foreign id columns to keep the model valid.

Ideal for embedded, multi-tenant analytics.

Endpoints

IBM IBM Db2: IBM relational database for transactional workloads.

GoodData: Composable analytics platform with headless BI and embedded dashboards.

How IBM IBM Db2 entities map to GoodData

IBM IBM Db2 entityGoodData objectNotes
tablesdb2_tablesid PK · custom fields → flattened columns
rowsdb2_rowsid PK · linked to db2_tables
schemasdb2_schemasid PK · linked to db2_tables
indexesdb2_indexesid PK · linked to db2_tables

FAQ

How does Datrise handle IBM IBM Db2's custom fields in GoodData?

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

How does the IBM IBM Db2 to GoodData sync stay up to date?

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

Related pipelines

Early access

Connect IBM IBM Db2 to GoodData 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.