DBMS > EsgynDB vs. HarperDB vs. Microsoft SQL Server vs. TerminusDB

System Properties Comparison EsgynDB vs. HarperDB vs. Microsoft SQL Server vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Microsofts flagship relational DBMS

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

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
RDF store

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	0.55
Rank	#248	Overall
	#38	Document stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

www.esgyn.cn

www.harperdb.io

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

terminusdb.com

Technical documentation

docs.harperdb.io/docs

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

terminusdb.github.io/terminusdb/#

Developer

Esgyn

HarperDB

Microsoft

DataChemist Ltd.

Initial release

2015

2017

1989

2018

Current release

3.1, August 2021

SQL Server 2022, November 2022

11.0.0, January 2023

License

Commercial or Open Source

commercial

free community edition available

commercial

restricted free version is available

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

C++, Java

Node.js

C++

Prolog, Rust

Server operating systems

Linux

Linux
OS X

Linux
Windows

Linux

Data scheme

yes

dynamic schema

yes

Typing

predefined data types such as float or date

yes

JSON data types

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 data manipulation statements

yes

SQL-like query language (WOQL)

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

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

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

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

JavaScript
Python

Server-side scripts

Stored procedures

Java Stored Procedures

Custom Functions

since release 3.1

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

A table resides as a whole on one (or more) nodes in a cluster

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

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

yes

the nodes on which a table resides can be defined

yes, but depending on the SQL-Server Edition

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

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

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

Access rights for users and roles

fine grained access rights according to SQL-standard

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.