DBMS > Databend vs. Greenplum vs. Microsoft Access vs. Riak KV vs. SAP HANA

System Properties Comparison Databend vs. Greenplum vs. Microsoft Access vs. Riak KV vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

An open-source, elastic, and workload-aware cloud data warehouse designed to meet businesses' massive-scale analytics needs at low cost and with low complexity

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.

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Distributed, fault tolerant key-value store

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

Primary database model

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational 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	0.34
Rank	#283	Overall
	#130	Relational DBMS

Score	8.08
Rank	#48	Overall
	#31	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

github.com/datafuselabs/databend
www.databend.com

greenplum.org

www.microsoft.com/en-us/microsoft-365/access

www.sap.com/products/hana.html

Technical documentation

docs.databend.com

docs.greenplum.org

developer.microsoft.com/en-us/access

www.tiot.jp/riak-docs/riak/kv/latest

help.sap.com/hana

Developer

Databend Labs

Pivotal Software Inc.

Microsoft

OpenSource, formerly Basho Technologies

SAP

Initial release

2021

2005

1992

2009

2010

Current release

1.0.59, April 2023

7.0.0, September 2023

1902 (16.0.11328.20222), March 2019

3.2.0, December 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

Open Source

Apache version 2, commercial enterprise edition

commercial

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

Rust

C++

Erlang

Server operating systems

hosted
Linux
macOS

Linux

Windows

Not a real database server, but making use of DLLs

Linux
OS X

Appliance or cloud-service

Data scheme

yes

schema-free

yes

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

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

APIs and other access methods

CLI Client
JDBC
RESTful HTTP API

JDBC
ODBC

ADO.NET
DAO
ODBC
OLE DB

HTTP API
Native Erlang Interface

JDBC
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
Python
Rust

C
Java
Perl
Python
R

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

Erlang

SQLScript, R

Triggers

yes

since Access 2010 using the ACE-engine

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

no "single point of failure"

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

none

selectable replication factor

yes

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

links between data sets can be stored

yes

Transaction concepts

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

yes

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

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

Users with fine-grained authorization concept, user roles

fine grained access rights according to SQL-standard

a simple user-level security was built in till version Access 2003

yes, using Riak Security

yes

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.