DBMS > CockroachDB vs. EsgynDB vs. Greenplum vs. Microsoft SQL Server vs. Oracle Rdb

System Properties Comparison CockroachDB vs. EsgynDB vs. Greenplum vs. Microsoft SQL Server vs. Oracle Rdb

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.

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

Microsofts flagship relational DBMS

Primary database model

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.08
Rank	#184	Overall
	#85	Relational DBMS

Website

www.cockroachlabs.com

www.esgyn.cn

greenplum.org

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

www.oracle.com/database/technologies/related/rdb.html

Technical documentation

www.cockroachlabs.com/docs

docs.greenplum.org

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

www.oracle.com/database/technologies/related/rdb-doc.html

Developer

Cockroach Labs

Esgyn

Pivotal Software Inc.

Microsoft

Oracle, originally developed by Digital Equipment Corporation (DEC)

Initial release

2015

2005

1989

1984

Current release

23.1.1, May 2023

7.0.0, September 2023

SQL Server 2022, November 2022

7.4.1.1, 2021

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

Open Source

Apache 2.0

commercial

restricted free version is available

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

C++

Server operating systems

Linux
macOS
Windows

Linux

Linux
Windows

HP Open VMS

Data scheme

dynamic schema

yes

Flexible Schema (defined schema, partial schema, schema free)

Typing

predefined data types such as float or date

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

since Version 4.2

yes

Secondary indexes

yes

SQL

Support of SQL

yes, wire compatible with PostgreSQL

yes

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC

JDBC
ODBC

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

Supported programming languages

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

All languages supporting JDBC/ODBC/ADO.Net

C
Java
Perl
Python
R

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

Server-side scripts

Stored procedures

Java Stored Procedures

yes

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

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Multi-source replication between multi datacenters

Source-replica replication

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

yes, on a single node

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.