Microsoft SQL Server to Azure Synapse Integration

How Datrise loads Microsoft SQL Server into Azure Synapse

Datrise syncs Microsoft SQL Server's tables, rows, schemas, indexes, primary keys, and change tracking 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

Microsoft SQL Server: Microsoft SQL Server transactional databases.

Azure Synapse: Microsoft analytics workspace with SQL pools.

How Microsoft SQL Server entities map to Azure Synapse

Microsoft SQL Server entity	Azure Synapse object	Notes
tables	`mssql_sql_server_tables`	id PK · custom fields → NVARCHAR(MAX) JSON columns
rows	`mssql_sql_server_rows`	id PK · linked to mssql_sql_server_tables
schemas	`mssql_sql_server_schemas`	id PK · linked to mssql_sql_server_tables
indexes	`mssql_sql_server_indexes`	id PK · linked to mssql_sql_server_tables

FAQ

How does Datrise handle Microsoft SQL Server'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 Microsoft SQL Server 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 Microsoft SQL Server 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.