Orbit to Azure Synapse Integration

How Datrise loads Orbit into Azure Synapse

Datrise syncs Orbit's members, activities, organizations, love scores, tags, and activity types into Azure Synapse as a typed table per source entity. Flexible or custom fields land in NVARCHAR(MAX) JSON columns, and timestamps such as created, updated, and status changes are typed as datetime2.

Sync is incremental: Datrise uses COPY into staging, then a MERGE on stable id, so re-runs update only what changed. Hash distribution on the join id with date partitioning on facts. Synapse dedicated pools reward good hash-distribution choices, so Datrise distributes on entity ids to avoid data-movement-heavy joins.

Ideal for Azure analytics estates feeding Power BI.

Endpoints

Orbit: Community member activity and engagement scoring.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Orbit entities map to Azure Synapse

Orbit entity	Azure Synapse object	Notes
members	`orbit_members`	id PK · custom fields → NVARCHAR(MAX) JSON columns
activities	`orbit_activities`	datetime2 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 Azure Synapse?

Flexible values are stored as NVARCHAR(MAX) JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Azure Synapse types.

How does the Orbit to Azure Synapse sync stay up to date?

It runs incrementally — Datrise uses COPY into staging, then a MERGE on stable id.

Related pipelines

Early access

Connect Orbit to Azure Synapse 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.