DBMS > BigchainDB vs. CockroachDB vs. Microsoft SQL Server vs. TimescaleDB

System Properties Comparison BigchainDB vs. CockroachDB vs. Microsoft SQL Server vs. TimescaleDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

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.

Microsofts flagship relational DBMS

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Document store

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Relational DBMS

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

Score	0.82
Rank	#212	Overall
	#36	Document stores

Score	6.10
Rank	#58	Overall
	#33	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	4.87
Rank	#74	Overall
	#4	Time Series DBMS

Website

www.bigchaindb.com

www.cockroachlabs.com

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

www.timescale.com

Technical documentation

bigchaindb.readthedocs.io/en/latest

www.cockroachlabs.com/docs

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

docs.timescale.com

Developer

Cockroach Labs

Microsoft

Timescale

Initial release

2016

2015

1989

2017

Current release

23.1.1, May 2023

SQL Server 2022, November 2022

2.13.0, November 2023

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache 2.0, commercial license available

commercial

restricted free version is available

Open Source

Apache 2.0

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

Python

C++

Server operating systems

Linux

Linux
macOS
Windows

Linux
Windows

Linux
OS X
Windows

Data scheme

schema-free

dynamic schema

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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, wire compatible with PostgreSQL

yes

full PostgreSQL SQL syntax

APIs and other access methods

CLI Client
RESTful HTTP API

JDBC

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

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

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

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

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

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication using RAFT

yes, but depending on the SQL-Server Edition

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

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,with MongoDB ord RethinkDB

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

yes

Role-based 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.