DBMS > Microsoft Azure Table Storage vs. Microsoft SQL Server vs. Percona Server for MySQL vs. PlanetScale vs. Valentina Server

System Properties Comparison Microsoft Azure Table Storage vs. Microsoft SQL Server vs. Percona Server for MySQL vs. PlanetScale vs. Valentina Server

Editorial information provided by DB-Engines

Name

Description

A Wide Column Store for rapid development using massive semi-structured datasets

Microsofts flagship relational DBMS

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Object-relational database and reports server

Primary database model

Wide column store

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	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	2.03
Rank	#122	Overall
	#57	Relational DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

azure.microsoft.com/en-us/services/storage/tables

www.microsoft.com/en-us/sql-server

www.percona.com/software/mysql-database/percona-server

planetscale.com

www.valentina-db.net

Technical documentation

learn.microsoft.com/en-US/sql/sql-server

www.percona.com/downloads/Percona-Server-LATEST

planetscale.com/docs

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Microsoft

Percona

PlanetScale

Paradigma Software

Initial release

2012

1989

2008

2020

1999

Current release

SQL Server 2022, November 2022

8.0.36-28, 2024

5.7.5

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

GPL version 2

commercial

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++

Server operating systems

hosted

Linux
Windows

Linux

Docker
Linux
macOS

Linux
OS X
Windows

Data scheme

schema-free

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

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

ODBC

Supported programming languages

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

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Ada
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication
XtraDB Cluster

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

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

optimistic locking

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

User concepts

Access control

Access rights based on private key authentication or shared access signatures

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

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.