mariadb
sqlserver

Migrate MariaDB to SQL Server

Certified — live-tested path

The converter maps 20 MariaDB column types to SQL Server. 4 of them change kind on the way (YEAR becomes SMALLINT, JSON becomes NVARCHAR(MAX), ENUM('a','b') becomes NVARCHAR(255), and more); the table below lists every one. DBShifts converts the schema, copies the rows in parallel batches and checks the result with row counts and checksums.

Start MariaDB → SQL Server Migration

Free tier · no credit card

MariaDB vs SQL Server

mariadb

MariaDB

the community-driven MySQL fork.

sqlserver

SQL Server

Microsoft's enterprise relational database.

MariaDB to SQL Server data type mapping

Pulled directly from DBShifts's own conversion rules — not a general reference table, this is what actually runs.

MariaDBSQL Server
INTINT
BIGINTBIGINT
SMALLINTSMALLINT
TINYINT(1)BIT
DECIMAL(10,2)DECIMAL(10,2)
FLOATFLOAT
DOUBLEFLOAT(53)
VARCHAR(255)NVARCHAR(255)
TEXTNVARCHAR(MAX)
LONGTEXTNVARCHAR(MAX)
CHAR(10)NCHAR(10)
DATEDATE
DATETIMEDATETIME2
TIMESTAMPDATETIMEOFFSET
TIMETIME
YEARSMALLINT
BLOBVARBINARY(MAX)
JSONNVARCHAR(MAX)
ENUM('a','b')NVARCHAR(255)
SET('a','b')NVARCHAR(MAX)

Example: MariaDB to SQL Server schema conversion

MariaDB

CREATE TABLE orders (
  id            INT AUTO_INCREMENT PRIMARY KEY,
  customer_id   INT NOT NULL,
  status        ENUM('new','paid','shipped') NOT NULL DEFAULT 'new',
  total         DECIMAL(10,2) NOT NULL,
  is_gift       TINYINT(1) NOT NULL DEFAULT 0,
  notes         TEXT,
  metadata      JSON,
  placed_at     DATETIME NOT NULL
);

SQL Server

IF OBJECT_ID(N'orders', 'U') IS NULL
CREATE TABLE [orders] (
    [id] INT IDENTITY(1,1) NOT NULL,
    [customer_id] INT NOT NULL,
    [status] NVARCHAR(255) NOT NULL DEFAULT N'new',
    [total] DECIMAL(10,2) NOT NULL,
    [is_gift] BIT NOT NULL DEFAULT 0,
    [notes] NVARCHAR(MAX),
    [metadata] NVARCHAR(MAX),
    [placed_at] DATETIME2 NOT NULL,
    CONSTRAINT [PK_orders] PRIMARY KEY ([id])
);

Moving to SQL Server usually means moving to a Microsoft stack

This direction is less common than the reverse and is normally driven by consolidation: an application is being absorbed into an estate that already runs SQL Server, Active Directory and reporting built on SSRS or Power BI. The database move is one part of a larger integration, which means the deadline is usually set by something other than the database.

The practical consequence is that the target schema is often not yours to design. Naming conventions, schema placement and audit columns may be dictated by the receiving estate, so plan for a mapping step rather than a direct copy.

Where MariaDB is more permissive than SQL Server

MariaDB accepts a great deal that SQL Server rejects. Zero dates such as 0000-00-00 are valid in MariaDB and impossible in SQL Server. Implicit conversion between strings and numbers is routine in MariaDB and an error in SQL Server. GROUP BY with unaggregated columns in the select list is permitted by MariaDB's default configuration and rejected outright by SQL Server.

Each of those is a data problem, not a schema problem, which means it surfaces during the load rather than during conversion. Zero dates in particular need a decision before the migration: they become NULL, a sentinel date, or the row is quarantined. Making that choice in advance is much cheaper than discovering it a third of the way through a load.

Unsigned integers are the other gap. MariaDB has them and SQL Server does not, so an unsigned column has to widen to the next larger signed type to keep values above the signed maximum. A BIGINT UNSIGNED holding values near its ceiling has no lossless destination and needs DECIMAL(20,0).

Storage engines and what does not come across

MariaDB storage engines have no SQL Server counterpart. Tables on MyISAM have no transactions and no foreign keys, so a schema that used MyISAM may have relationships that were never enforced and data that does not satisfy them. Those orphans appear when foreign keys are applied on the target.

MariaDB's own extensions, notably Aria, Sequence and Spider engines, and its system-versioned tables, are MariaDB-specific. System-versioned history is queryable data that a plain table copy will not bring along, so decide explicitly whether the history is being migrated or dropped.

MariaDB → SQL Server conversion notes

Engine-specific rules baked into the conversion and transfer pipeline — verified by live certification of this exact pair.

  • MariaDB's JSON columns (LONGTEXT + json_valid CHECK) are detected and mapped to real JSON types on targets that have them.
  • Engine-specific CHECK constraints like json_valid() are filtered on targets that don't support them — data still migrates.
  • Display-width unsigned types (bigint(20) unsigned) are recognized and widened correctly.
  • IDENTITY_INSERT is managed per table so explicit IDs from the source load correctly, then counters are reseeded with DBCC CHECKIDENT.
  • Binary columns always carry an explicit length — bare VARBINARY (which means 1 byte) never reaches the target.
  • TRUNCATE falls back to DELETE on FK-referenced tables automatically.

Frequently asked questions

Is MariaDB to SQL Server migration production-ready in DBShifts?

Yes. MariaDB to SQL Server is a certified pair: it passes the live certification suite on real MariaDB and SQL Server servers, which checks schema fidelity, row counts, type-aware checksums and paging across batches.

What happens to MariaDB types that SQL Server doesn't have?

Each gets the nearest SQL Server type the converter treats as safe: YEAR becomes SMALLINT, JSON becomes NVARCHAR(MAX), ENUM('a','b') becomes NVARCHAR(255), SET('a','b') becomes NVARCHAR(MAX). Every such decision is in the migration plan before anything runs, and any mapping can be overridden per column.

Can I keep MariaDB and SQL Server in sync after the initial migration?

Yes, until you cut over. DBShifts reads the row-based binary log (binlog_format = ROW). With zero-downtime mode on, the log position is captured before the first row is copied, so writes made during the copy are replayed afterwards.

Which MariaDB data types need a second look when moving to SQL Server?

The table above carries a note on 9 of them: TINYINT(1) (BIT), FLOAT (FLOAT), DOUBLE (FLOAT(53)), TIMESTAMP (DATETIMEOFFSET) and more. Analysis flags the same columns on your own schema before any data moves.

Go deeper

Ready to move MariaDB to SQL Server?

Set up in under two minutes. Validation and rollback included.

Start Free Migration