DatriseAI-first ETL

Desk Com Azure Synapse

AI-first ETL from Desk Com into Azure Synapse. Governed entities, incremental sync, typed landing tables.

How Datrise loads Desk Com into Azure Synapse

Datrise syncs Desk Com's records, events, and configuration objects 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

Desk Com: SaaS or API data source for analytics and warehouse sync.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Desk Com entities map to Azure Synapse

Desk Com entityAzure Synapse objectNotes
recordsdesk_com_recordsid PK · custom fields → NVARCHAR(MAX) JSON columns
eventsdesk_com_eventsdatetime2 events
configuration objectsdesk_com_configuration_objectsid PK · linked to desk_com_records

FAQ

How does Datrise handle Desk Com'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 Desk Com 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 Desk Com 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.