DatriseAI-first ETL

CockroachDB to GoodData Integration

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

How Datrise loads CockroachDB into GoodData

Datrise syncs CockroachDB's tables, rows, schemas, secondary indexes, ranges, and change feeds 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

CockroachDB: Distributed SQL with survivable multi-region consistency.

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

How CockroachDB entities map to GoodData

CockroachDB entityGoodData objectNotes
tablescockroachdb_tablesid PK · custom fields → flattened columns
rowscockroachdb_rowsid PK · linked to cockroachdb_tables
schemascockroachdb_schemasid PK · linked to cockroachdb_tables
secondary indexescockroachdb_secondary_indexesid PK · linked to cockroachdb_tables

FAQ

How does Datrise handle CockroachDB'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 CockroachDB to GoodData sync stay up to date?

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

Related pipelines

Early access

Connect CockroachDB 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.