MariaDB Features Not Available in SQL Server

Some MariaDB features are not available in SQL Server.

At first glance, it is not important to know about those features to migrate from SQL Server to MariaDB. However, this is not the case. Using MariaDB features that are not in SQL Server allows one to obtain more advantages from the migration, getting the most from MariaDB.

This page has a list of MariaDB features that are not supported in SQL Server. The list is not exhaustive.

Plugin Architecture

• Storage engines.

• .

• .

• is a columnar storage engine designed to scale horizontally. It runs on a specific edition of MariaDB, so currently it cannot be used in combination with other engines.

• The variable determines in which cases an SQL statement should fail with an error, and in which cases it should succeed with a warning even if it is not entirely correct. For example, when a statement tries to insert a string in a column which is not big enough to contain it, it could fail, or it could insert a truncated string and emit a warning. It is a tradeoff between reliability and flexibility.

  • allows one to use a small subset of SQL Server proprietary syntax.

• The options are supported for most .

See also .

• don't depend on column type. They can be set globally, or at database, table or column level.

• Columns may use non-constant expressions as the value. columns may have a DEFAULT value.

• numeric types.

See also .

For compatibility with some other database systems, MariaDB supports the pseudo-type. However, it is just an alias for:

LONGTEXT CHECK (JSON_VALID(column_name))

is the MariaDB equivalent of SQL Server's ISJSON().

• functionality allows one to "undo" the changes that happened after a certain point in time.

• support the following features:

  • Tables can be partitioned based on .

_{This page is licensed: CC BY-SA / Gnu FDL}