DatriseAI-first ETL

Excel File to Azure Synapse Integration

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

How Datrise loads Excel File into Azure Synapse

Datrise syncs Excel File's worksheets, rows, columns, headers, cell ranges, and workbooks 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

Excel File: Spreadsheet workbooks from exports and shared drives.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Excel File entities map to Azure Synapse

Excel File entityAzure Synapse objectNotes
worksheetsexcel_file_worksheetsid PK · custom fields → NVARCHAR(MAX) JSON columns
rowsexcel_file_rowsid PK · linked to excel_file_worksheets
columnsexcel_file_columnsid PK · linked to excel_file_worksheets
headersexcel_file_headersid PK · linked to excel_file_worksheets

FAQ

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