Microsoft SQL Server to Databricks SQL Warehouse Integration
AI-first ETL from Microsoft SQL Server into Databricks SQL Warehouse. Governed entities, incremental sync, typed landing tables.
How Datrise loads Microsoft SQL Server into Databricks SQL Warehouse
Datrise syncs Microsoft SQL Server's tables, rows, schemas, indexes, primary keys, and change tracking into Databricks SQL Warehouse as a Delta Lake table per source entity. Flexible or custom fields land in VARIANT or STRUCT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP.
Sync is incremental: Datrise uses a Delta MERGE on stable id, with change history available via time travel, so re-runs update only what changed. Delta partitioning by load date with OPTIMIZE/Z-ORDER on query keys. Datrise writes Unity Catalog–governed Delta tables, so lineage and permissions are managed centrally rather than per-notebook.
Ideal for lakehouse analytics and ML feature tables on Databricks.
Endpoints
Microsoft SQL Server: Microsoft SQL Server transactional databases.
Databricks SQL Warehouse: Lakehouse SQL endpoints over Delta tables.
How Microsoft SQL Server entities map to Databricks SQL Warehouse
| Microsoft SQL Server entity | Databricks SQL Warehouse object | Notes |
|---|---|---|
| tables | mssql_sql_server_tables | id PK · custom fields → VARIANT or STRUCT 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 Databricks SQL Warehouse?
Flexible values are stored as VARIANT or STRUCT columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Databricks SQL Warehouse types.
How does the Microsoft SQL Server to Databricks SQL Warehouse sync stay up to date?
It runs incrementally — Datrise uses a Delta MERGE on stable id, with change history available via time travel.
Related pipelines
More destinations for Microsoft SQL Server
- Microsoft SQL Server → ClickHouse
- Microsoft SQL Server → DuckDB
- Microsoft SQL Server → Amazon Athena
- Microsoft SQL Server → Amazon S3 Data Lake
- Microsoft SQL Server → Azure Data Lake Storage
- Microsoft SQL Server → Azure Synapse
- Microsoft SQL Server → Spreadsheets
- Microsoft SQL Server → Airtable
- Microsoft SQL Server → CSV Files
- Microsoft SQL Server → MongoDB
- Microsoft SQL Server → Supabase
- Microsoft SQL Server → Neon
More sources for Databricks SQL Warehouse
- My Hours → Databricks SQL Warehouse
- n8n → Databricks SQL Warehouse
- NetSuite SuiteAnalytics → Databricks SQL Warehouse
- New York Times → Databricks SQL Warehouse
- News API → Databricks SQL Warehouse
- Newsdata → Databricks SQL Warehouse
- Notion → Databricks SQL Warehouse
- Okta → Databricks SQL Warehouse
- Omnisend → Databricks SQL Warehouse
- Onesignal → Databricks SQL Warehouse
- Onfleet → Databricks SQL Warehouse
- Openweather → Databricks SQL Warehouse
Early access
Connect Microsoft SQL Server to Databricks SQL Warehouse 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.