The Ultimate Guide to High Availability with MariaDB

SQL Server features not available in MariaDB

You are viewing an old version of this article. View the current version here.

When planning a migration between different DBMSs, one of the most important aspects to consider is that the new database system will probably miss some features supported by the old one. This is not relevant for all users. The most widely used features are supported by most DBMSs. However, it is important to make a list of unsupported features and check which of them are currently used by applications. In most cases it is possible to implement such features on the application side, or simply stop using them.

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

Contents

  1. Introduced in SQL Server 2016 or older
  2. Introduced in SQL Server 2017
  3. Introduced in SQL Server 2019

Introduced in SQL Server 2016 or older

  • MERGE
  • User-Defined Types
  • Rules
  • Triggers on DDL and login; INSTEAD OF triggers, DISABLE TRIGGER
  • Synonyms
  • Queues
  • XML indexes, XML schema collection, XQuery

Introduced in SQL Server 2017

  • Adaptive joins
  • External libraries (MariaDB only supports procedural SQL and PL/SQL)

Introduced in SQL Server 2019

  • External languages (MariaDB only supports procedural SQL and PL/SQL)

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.