DBMS > Greenplum vs. HarperDB vs. Microsoft Access vs. MySQL

System Properties Comparison Greenplum vs. HarperDB vs. Microsoft Access vs. MySQL

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.

HarperDB takes the "stack" out of "tech stack" by combining an ultra-fast document-style data store, in-memory cache, real-time message broker, and your application components into a single distributed technology.

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.)

Widely used open source RDBMS

Primary database model

Relational DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	7.71
Rank	#46	Overall
	#29	Relational DBMS

Score	0.55
Rank	#243	Overall
	#38	Document stores

Score	93.76
Rank	#12	Overall
	#8	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

greenplum.org

www.harperdb.io

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

www.mysql.com

Technical documentation

docs.greenplum.org

docs.harperdb.io/docs

developer.microsoft.com/en-us/access

dev.mysql.com/doc

Developer

Pivotal Software Inc.

HarperDB

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2005

2017

1992

1995

Current release

7.0.0, September 2023

3.1, August 2021

1902 (16.0.11328.20222), March 2019

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

free community edition available

commercial

Bundled with Microsoft Office

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

Node.js

C++

C and C++

Server operating systems

Linux

Linux
OS X

Windows

Not a real database server, but making use of DLLs

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

dynamic schema

yes

Typing

predefined data types such as float or date

yes

JSON data types

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

SQL-like data manipulation statements

yes

but not compliant to any SQL standard

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

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

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

Custom Functions

since release 3.1

yes

since Access 2010 using the ACE-engine

yes

proprietary syntax

Triggers

yes

since Access 2010 using the ACE-engine

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

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

the nodes on which a table resides can be defined

none

Multi-source replication
Source-replica replication

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

not for MyISAM storage engine

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

but no files for transaction logging

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

yes, using LMDB

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

fine grained access rights according to SQL-standard

Access rights for users and roles

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

Users with fine-grained authorization concept

no user groups or roles

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.