Microsoft SQL Server to MySQL Integration

How Datrise loads Microsoft SQL Server into MySQL

Datrise syncs Microsoft SQL Server's tables, rows, schemas, indexes, primary keys, and change tracking into MySQL as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME/TIMESTAMP.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.

Ideal for operational reporting and app databases already standardized on MySQL.

Endpoints

Microsoft SQL Server: Microsoft SQL Server transactional databases.

MySQL: Widely used OSS relational engine (InnoDB).

How Microsoft SQL Server entities map to MySQL

Microsoft SQL Server entity	MySQL object	Notes
tables	`mssql_sql_server_tables`	id PK · custom fields → 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 MySQL?

Flexible values are stored as JSON columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native MySQL types.

How does the Microsoft SQL Server to MySQL sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.

Related pipelines

Early access

Connect Microsoft SQL Server to MySQL 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.