DBMS > Badger vs. Dolt vs. HEAVY.AI vs. Microsoft SQL Server vs. Sequoiadb

System Properties Comparison Badger vs. Dolt vs. HEAVY.AI vs. Microsoft SQL Server vs. Sequoiadb

Editorial information provided by DB-Engines

Name

Description

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

A MySQL compatible DBMS with Git-like versioning of data and schema

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Microsofts flagship relational DBMS

NewSQL database with distributed OLTP and SQL

Primary database model

Key-value store

Relational DBMS

Document store
Relational DBMS

Secondary database models

Document store

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	0.14
Rank	#331	Overall
	#49	Key-value stores

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Website

github.com/dgraph-io/badger

github.com/dolthub/dolt
www.dolthub.com

github.com/heavyai/heavydb
www.heavy.ai

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

www.sequoiadb.com

Technical documentation

godoc.org/github.com/dgraph-io/badger

docs.dolthub.com

docs.heavy.ai

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

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

DGraph Labs

DoltHub Inc

HEAVY.AI, Inc.

Microsoft

Sequoiadb Ltd.

Initial release

2017

2018

2016

1989

2013

Current release

5.10, January 2022

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2.0

Open Source

Apache Version 2; enterprise edition available

commercial

restricted free version is available

Open Source

Server: AGPL; Client: Apache V2

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

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Linux

Linux
Windows

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

APIs and other access methods

CLI Client
HTTP REST

JDBC
ODBC
Thrift
Vega

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

proprietary protocol using JSON

Supported programming languages

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

All languages supporting JDBC/ODBC/Thrift
Python

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

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

yes

currently in alpha release

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

JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Round robin

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Multi-source replication

yes, but depending on the SQL-Server Edition

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Document is locked during a transaction

Concurrency

Support for concurrent manipulation of data

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

Only one user is configurable, and must be specified in the config file at startup

fine grained access rights according to SQL-standard

simple password-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.