Orbit to Databricks SQL Warehouse Integration

How Datrise loads Orbit into Databricks SQL Warehouse

Datrise syncs Orbit's members, activities, organizations, love scores, tags, and activity types into Databricks SQL Warehouse as a Delta Lake table per source entity. Flexible or custom fields land in VARIANT or STRUCT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP.

Sync is incremental: Datrise uses a Delta MERGE on stable id, with change history available via time travel, so re-runs update only what changed. Delta partitioning by load date with OPTIMIZE/Z-ORDER on query keys. Datrise writes Unity Catalog–governed Delta tables, so lineage and permissions are managed centrally rather than per-notebook.

Ideal for lakehouse analytics and ML feature tables on Databricks.

Endpoints

Orbit: Community member activity and engagement scoring.

Databricks SQL Warehouse: Lakehouse SQL endpoints over Delta tables.

How Orbit entities map to Databricks SQL Warehouse

Orbit entity	Databricks SQL Warehouse object	Notes
members	`orbit_members`	id PK · custom fields → VARIANT or STRUCT columns
activities	`orbit_activities`	TIMESTAMP events
organizations	`orbit_organizations`	id PK · linked to orbit_members
love scores	`orbit_love_scores`	id PK · linked to orbit_members

FAQ

How does Datrise handle Orbit's custom fields in Databricks SQL Warehouse?

Flexible values are stored as VARIANT or STRUCT columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Databricks SQL Warehouse types.

How does the Orbit to Databricks SQL Warehouse sync stay up to date?

It runs incrementally — Datrise uses a Delta MERGE on stable id, with change history available via time travel.

Related pipelines

Early access

Connect Orbit to Databricks SQL Warehouse 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.