DBMS > EJDB vs. Heroic vs. Microsoft SQL Server vs. MonetDB vs. mSQL

System Properties Comparison EJDB vs. Heroic vs. Microsoft SQL Server vs. MonetDB vs. mSQL

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Microsofts flagship relational DBMS

A relational database management system that stores data in columns

mSQL (Mini SQL) is a simple and lightweight RDBMS

Primary database model

Document store

Time Series 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	0.27
Rank	#297	Overall
	#44	Document stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.72
Rank	#145	Overall
	#67	Relational DBMS

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Website

github.com/Softmotions/ejdb

github.com/spotify/heroic

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

www.monetdb.org

hughestech.com.au/products/msql

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

spotify.github.io/heroic

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

www.monetdb.org/Documentation

Developer

Softmotions

Spotify

Microsoft

MonetDB BV

Hughes Technologies

Initial release

2012

2014

1989

2004

1994

Current release

SQL Server 2022, November 2022

Dec2023 (11.49), December 2023

4.4, October 2021

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

Mozilla Public License 2.0

commercial

free licenses can be provided

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

Java

C++

Server operating systems

server-less

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

via Elasticsearch

yes

SQL

Support of SQL

yes

SQL 2003 with some extensions

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

APIs and other access methods

in-process shared library

HQL (Heroic Query Language, a JSON-based language)
HTTP API

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

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

JDBC
ODBC

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

C
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

C
C++
Delphi
Java
Perl
PHP
Tcl

Server-side scripts

Stored procedures

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

yes, in SQL, C, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

Sharding via remote tables

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

yes, but depending on the SQL-Server Edition

none

Source-replica replication available in experimental status

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

none

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

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

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.