DBMS > CockroachDB vs. IBM Db2 warehouse vs. Microsoft SQL Server vs. TimescaleDB

System Properties Comparison CockroachDB vs. IBM Db2 warehouse vs. Microsoft SQL Server vs. TimescaleDB

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.

Cloud-based data warehousing service

Microsofts flagship relational DBMS

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

Primary database model

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	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	1.30
Rank	#164	Overall
	#75	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

www.cockroachlabs.com

www.ibm.com/products/db2/warehouse

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

www.timescale.com

Technical documentation

www.cockroachlabs.com/docs

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

docs.timescale.com

Developer

Cockroach Labs

IBM

Microsoft

Timescale

Initial release

2015

2014

1989

2017

Current release

23.1.1, May 2023

SQL Server 2022, November 2022

2.15.0, May 2024

License

Commercial or Open Source

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

yes

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

Server operating systems

Linux
macOS
Windows

hosted

Linux
Windows

Linux
OS X
Windows

Data scheme

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.

Import/export of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes, wire compatible with PostgreSQL

yes

full PostgreSQL SQL syntax

APIs and other access methods

JDBC

.NET Client API
JDBC
ODBC
OLE DB

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

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

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

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

PL/SQL, SQL PL

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

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

Sharding

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

Multi-source replication using RAFT

yes

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

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

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.