DatriseAI-first ETL

Workday Azure Synapse

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

How Datrise loads Workday into Azure Synapse

Datrise syncs Workday's HR, finance entities, organizational structures, and operational events 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

Workday: Enterprise HR and finance source for operational reporting.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Workday entities map to Azure Synapse

Workday entityAzure Synapse objectNotes
HRworkday_hrid PK · custom fields → NVARCHAR(MAX) JSON columns
finance entitiesworkday_finance_entitiesid PK · linked to workday_hr
organizational structuresworkday_organizational_structuresid PK · linked to workday_hr
operational eventsworkday_operational_eventsdatetime2 events

FAQ

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