DBMS > EsgynDB vs. Microsoft SQL Server vs. Percona Server for MySQL vs. SWC-DB vs. TerminusDB

System Properties Comparison EsgynDB vs. Microsoft SQL Server vs. Percona Server for MySQL vs. SWC-DB vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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.

A high performance, scalable Wide Column DBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Relational DBMS

Wide column store

Graph DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Time Series DBMS

Document store
RDF store

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

Score	0.23
Rank	#319	Overall
	#141	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	2.21
Rank	#121	Overall
	#58	Relational DBMS

Score	0.01
Rank	#387	Overall
	#13	Wide column stores

Score	0.22
Rank	#323	Overall
	#28	Graph DBMS

Website

www.esgyn.cn

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

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

github.com/kashirin-alex/swc-db
www.swcdb.org

terminusdb.com

Technical documentation

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

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

terminusdb.github.io/terminusdb/#

Developer

Esgyn

Microsoft

Percona

Alex Kashirin

DataChemist Ltd.

Initial release

2015

1989

2008

2020

2018

Current release

SQL Server 2022, November 2022

8.0.36-28, 2024

0.5, April 2021

11.0.0, January 2023

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

GPL version 2

Open Source

GPL V3

Open Source

GPL V3

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++, Java

C++

C and C++

C++

Prolog, Rust

Server operating systems

Linux

Linux
Windows

Linux

Data scheme

yes

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

SQL-like query language

SQL-like query language (WOQL)

APIs and other access methods

ADO.NET
JDBC
ODBC

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

ADO.NET
JDBC
ODBC

Proprietary protocol
Thrift

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

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

C++

JavaScript
Python

Server-side scripts

Stored procedures

Java Stored Procedures

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

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication
XtraDB Cluster

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

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

Role-based access control

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.