DBMS > Greenplum vs. HarperDB vs. SAP HANA vs. TimescaleDB

System Properties Comparison Greenplum vs. HarperDB vs. SAP HANA vs. TimescaleDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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.

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

In-memory, column based data store. Available as appliance or cloud service

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

Primary database model

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Relational DBMS

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

Score	8.08
Rank	#48	Overall
	#31	Relational DBMS

Score	0.60
Rank	#244	Overall
	#38	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

greenplum.org

www.harperdb.io

www.sap.com/products/hana.html

www.timescale.com

Technical documentation

docs.greenplum.org

docs.harperdb.io/docs

help.sap.com/hana

docs.timescale.com

Developer

Pivotal Software Inc.

HarperDB

SAP

Timescale

Initial release

2005

2017

2010

2017

Current release

7.0.0, September 2023

3.1, August 2021

2.0 SPS07 (April 4, 2023), April 2023

2.15.0, May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

free community edition available

commercial

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Node.js

Server operating systems

Linux

Linux
OS X

Appliance or cloud-service

Linux
OS X
Windows

Data scheme

yes

dynamic schema

yes

Typing

predefined data types such as float or date

yes

JSON data types

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

since Version 4.2

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like data manipulation statements

yes

full PostgreSQL SQL syntax

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

JDBC
ODBC

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

Supported programming languages

C
Java
Perl
Python
R

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

Custom Functions

since release 3.1

SQLScript, R

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

A table resides as a whole on one (or more) nodes in a cluster

yes

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

the nodes on which a table resides can be defined

yes

Source-replica replication with hot standby and reads on replicas

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

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

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

Access rights for users and roles

yes

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.