DBMS > CockroachDB vs. Microsoft SQL Server vs. NSDb vs. SAP SQL Anywhere vs. TigerGraph

System Properties Comparison CockroachDB vs. Microsoft SQL Server vs. NSDb vs. SAP SQL Anywhere vs. TigerGraph

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.

Microsofts flagship relational DBMS

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

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	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

www.cockroachlabs.com

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

nsdb.io

www.sap.com/products/technology-platform/sql-anywhere.html

www.tigergraph.com

Technical documentation

www.cockroachlabs.com/docs

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

nsdb.io/Architecture

help.sap.com/docs/SAP_SQL_Anywhere

docs.tigergraph.com

Developer

Cockroach Labs

Microsoft

SAP

formerly Sybase

Initial release

2015

1989

2017

1992

2017

Current release

23.1.1, May 2023

SQL Server 2022, November 2022

17, July 2015

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

restricted free version is available

Open Source

Apache Version 2.0

commercial

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

Java, Scala

C++

Server operating systems

Linux
macOS
Windows

Linux
Windows

Linux
macOS

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux

Data scheme

dynamic schema

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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

all fields are automatically indexed

yes

SQL

Support of SQL

yes, wire compatible with PostgreSQL

yes

SQL-like query language

yes

SQL-like query language (GSQL)

APIs and other access methods

JDBC

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

gRPC
HTTP REST
WebSocket

ADO.NET
HTTP API
JDBC
ODBC

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

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

Java
Scala

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

C++
Java

Server-side scripts

Stored procedures

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

yes, in C/C++, Java, .Net or Perl

yes

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

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

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

yes, but depending on the SQL-Server Edition

Source-replica replication

Database mirroring

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

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

Using Apache Lucene

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

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