DatriseAI-first ETL

Dixa Azure Synapse

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

How Datrise loads Dixa into Azure Synapse

Datrise syncs Dixa's conversations, agents, customers, tags, and resolution metrics 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

Dixa: Customer service platform for conversations across channels.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Dixa entities map to Azure Synapse

Dixa entityAzure Synapse objectNotes
conversationsdixa_conversationsid PK · custom fields → NVARCHAR(MAX) JSON columns
agentsdixa_agentsid PK · linked to dixa_conversations
customersdixa_customersid PK · linked to dixa_conversations
tagsdixa_tagsid PK · linked to dixa_conversations

FAQ

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