DBMS > Hypertable vs. IBM Db2 vs. Microsoft Access vs. Microsoft Azure Cosmos DB

System Properties Comparison Hypertable vs. IBM Db2 vs. Microsoft Access vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

Description

An open source BigTable implementation based on distributed file systems such as Hadoop

Common in IBM host environments, 2 different versions for host and Windows/Linux

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

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Wide column store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

Spatial DBMS

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

Score	128.46
Rank	#8	Overall
	#5	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

www.ibm.com/products/db2

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

azure.microsoft.com/services/cosmos-db

Technical documentation

www.ibm.com/docs/en/db2

developer.microsoft.com/en-us/access

learn.microsoft.com/azure/cosmos-db

Developer

Hypertable Inc.

IBM

Microsoft

Initial release

2009

1983

host version

1992

2014

Current release

0.9.8.11, March 2016

12.1, October 2016

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

GNU version 3. Commercial license available

commercial

free version is available

commercial

Bundled with Microsoft Office

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

C and C++

C++

Server operating systems

Linux
OS X
Windows

an inofficial Windows port is available

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Windows

Not a real database server, but making use of DLLs

hosted

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

Secondary indexes

restricted

only exact value or prefix value scans

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like query language

APIs and other access methods

C++ API
Thrift

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

ADO.NET
DAO
ODBC
OLE DB

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

C++
Java
Perl
PHP
Python
Ruby

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

JavaScript

Triggers

yes

since Access 2010 using the ACE-engine

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor on file system level

yes

with separate tools (MQ, InfoSphere)

none

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

but no files for transaction logging

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

User concepts

Access control

fine grained access rights according to SQL-standard

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

Access rights can be defined down to the item level

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.