DBMS > Greenplum vs. Oracle NoSQL vs. SAP HANA vs. Warp 10

System Properties Comparison Greenplum vs. Oracle NoSQL vs. SAP HANA vs. Warp 10

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.

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Relational DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	7.71
Rank	#46	Overall
	#29	Relational DBMS

Score	3.07
Rank	#86	Overall
	#15	Document stores
	#11	Key-value stores
	#47	Relational DBMS

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Score	0.06
Rank	#351	Overall
	#35	Time Series DBMS

Website

greenplum.org

www.oracle.com/database/nosql/technologies/nosql

www.sap.com/products/hana.html

www.warp10.io

Technical documentation

docs.greenplum.org

docs.oracle.com/en/database/other-databases/nosql-database/index.html

help.sap.com/hana

www.warp10.io/content/02_Getting_started

Developer

Pivotal Software Inc.

Oracle

SAP

SenX

Initial release

2005

2011

2010

2015

Current release

7.0.0, September 2023

24.1, May 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

commercial

Open Source

Apache License 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

Java

Server operating systems

Linux

Linux
Solaris SPARC/x86

Appliance or cloud-service

Linux
OS X
Windows

Data scheme

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

JDBC
ODBC

HTTP API
Jupyter
WebSocket

Supported programming languages

C
Java
Perl
Python
R

C
C#
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

SQLScript, R

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

yes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

configurable

ACID within a storage node (=shard)

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

off heap cache

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

yes

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.