DBMS > Greenplum vs. KeyDB vs. Microsoft SQL Server vs. Trafodion

System Properties Comparison Greenplum vs. KeyDB vs. Microsoft SQL Server vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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.

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Microsofts flagship relational DBMS

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

Key-value store

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	8.08
Rank	#48	Overall
	#31	Relational DBMS

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Website

greenplum.org

github.com/Snapchat/KeyDB
keydb.dev

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

trafodion.apache.org

Technical documentation

docs.greenplum.org

docs.keydb.dev

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

trafodion.apache.org/documentation.html

Developer

Pivotal Software Inc.

EQ Alpha Technology Ltd.

Microsoft

Apache Software Foundation, originally developed by HP

Initial release

2005

2019

1989

2014

Current release

7.0.0, September 2023

SQL Server 2022, November 2022

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

BSD-3

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.

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

C++, Java

Server operating systems

Linux

Linux
Windows

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

yes

SQL

Support of SQL

yes

APIs and other access methods

JDBC
ODBC

Proprietary protocol

RESP - REdis Serialization Protoco

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

ADO.NET
JDBC
ODBC

Supported programming languages

C
Java
Perl
Python
R

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

Lua

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

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

yes, but depending on the SQL-Server Edition

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

fine grained access rights according to SQL-standard

simple password-based access control and ACL

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.