DBMS > CockroachDB vs. HarperDB vs. Microsoft SQL Server vs. Riak KV

System Properties Comparison CockroachDB vs. HarperDB vs. Microsoft SQL Server vs. Riak KV

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

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

Distributed, fault tolerant key-value store

Primary database model

with links between data sets and object tags for the creation of secondary indexes

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	0.55
Rank	#248	Overall
	#38	Document stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Website

www.cockroachlabs.com

www.harperdb.io

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

Technical documentation

www.cockroachlabs.com/docs

docs.harperdb.io/docs

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

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Cockroach Labs

HarperDB

Microsoft

OpenSource, formerly Basho Technologies

Initial release

2015

2017

1989

2009

Current release

23.1.1, May 2023

3.1, August 2021

SQL Server 2022, November 2022

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

free community edition available

commercial

restricted free version is available

Open Source

Apache version 2, commercial enterprise edition

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

Node.js

C++

Erlang

Server operating systems

Linux
macOS
Windows

Linux
OS X

Linux
Windows

Linux
OS X

Data scheme

dynamic schema

yes

schema-free

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

restricted

SQL

Support of SQL

yes, wire compatible with PostgreSQL

SQL-like data manipulation statements

yes

APIs and other access methods

JDBC

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

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

HTTP API
Native Erlang Interface

Supported programming languages

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

.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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

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

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

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

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

yes

the nodes on which a table resides can be defined

yes, but depending on the SQL-Server Edition

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

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 capabilities

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

yes

User concepts

Access control

Role-based access control

Access rights for users and roles

fine grained access rights according to SQL-standard

yes, using Riak Security

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.