DBMS > Microsoft Azure SQL Database vs. MySQL vs. OpenQM vs. VoltDB

System Properties Comparison Microsoft Azure SQL Database vs. MySQL vs. OpenQM vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering with high compatibility to Microsoft SQL Server

Widely used open source RDBMS

QpenQM is a high-performance, self-tuning, multi-value DBMS

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Key/Value like access via memcached API

Multivalue DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	72.95
Rank	#16	Overall
	#11	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.28
Rank	#291	Overall
	#10	Multivalue DBMS

Score	1.38
Rank	#156	Overall
	#72	Relational DBMS

Website

azure.microsoft.com/en-us/products/azure-sql/database

www.mysql.com

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.voltdb.com

Technical documentation

docs.microsoft.com/en-us/azure/azure-sql

dev.mysql.com/doc

docs.voltdb.com

Developer

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Rocket Software, originally Martin Phillips

VoltDB Inc.

Initial release

2010

1995

1993

2010

Current release

V12

9.0.0, July 2024

3.4-12

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPLv2, extended commercial license available

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

C and C++

Java, C++

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
OS X

for development

Data scheme

yes

with some exceptions

yes

Typing

predefined data types such as float or date

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

only a subset of SQL 99

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
Basic
C
Java
Objective C
PHP
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

Transact SQL

yes

proprietary syntax

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with always 3 replicas available

Multi-source replication
Source-replica replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

FOREIGN KEY constraints are not supported

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

not for MyISAM storage engine

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

Access rights can be defined down to the item level

Users and roles with access to stored procedures

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.