DatriseAI-first ETL

Visma E Conomic Azure Synapse

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

How Datrise loads Visma E Conomic into Azure Synapse

Datrise syncs Visma E Conomic'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

Visma E Conomic: SaaS or API data source for analytics and warehouse sync.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Visma E Conomic entities map to Azure Synapse

Visma E Conomic entityAzure Synapse objectNotes
recordsvisma_e_conomic_recordsid PK · custom fields → NVARCHAR(MAX) JSON columns
eventsvisma_e_conomic_eventsdatetime2 events
configuration objectsvisma_e_conomic_configuration_objectsid PK · linked to visma_e_conomic_records

FAQ

How does Datrise handle Visma E Conomic'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 Visma E Conomic 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 Visma E Conomic 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.