DBMS > ClickHouse vs. Microsoft Access vs. Microsoft Azure Table Storage vs. Oracle NoSQL vs. VoltDB

System Properties Comparison ClickHouse vs. Microsoft Access vs. Microsoft Azure Table Storage vs. Oracle NoSQL vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

A high-performance, column-oriented SQL DBMS for online analytical processing (OLAP) that uses all available system resources to their full potential to process each analytical query as fast as possible. It is available as both an open-source software and a cloud offering.

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

A Wide Column Store for rapid development using massive semi-structured datasets

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Wide column store

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	15.55
Rank	#38	Overall
	#23	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

clickhouse.com

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

azure.microsoft.com/en-us/services/storage/tables

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

www.voltdb.com

Technical documentation

clickhouse.com/docs

developer.microsoft.com/en-us/access

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

docs.voltdb.com

Developer

Clickhouse Inc.

Microsoft

Oracle

VoltDB Inc.

Initial release

2016

1992

2012

2011

2010

Current release

v24.4.2.141-stable, June 2024

1902 (16.0.11328.20222), March 2019

24.1, May 2024

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

commercial

Open Source

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

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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.

Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.
DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
ClickHouse Cloud: Get the performance you love from open source ClickHouse in a serverless offering that takes care of the details so you can spend more time getting insight out of the fastest database on earth.

Implementation language

C++

Java

Java, C++

Server operating systems

FreeBSD
Linux
macOS

Windows

Not a real database server, but making use of DLLs

hosted

Linux
Solaris SPARC/x86

Linux
OS X

for development

Data scheme

yes

schema-free

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

yes

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.

Secondary indexes

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

yes

but not compliant to any SQL standard

SQL-like DML and DDL statements

yes

only a subset of SQL 99

APIs and other access methods

gRPC
HTTP REST
JDBC
MySQL wire protocol
ODBC
PostgreSQL wire protocol
Proprietary protocol

ADO.NET
DAO
ODBC
OLE DB

RESTful HTTP API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

3rd party library
C++
Elixir

3rd party library
Go

3rd party library
Java

3rd party library
JavaScript (Node.js)

3rd party library
Kotlin

3rd party library
Nim

3rd party library
Perl

3rd party library
PHP

3rd party library
Python

3rd party library
R

3rd party library
Ruby

3rd party library
Rust
Scala

3rd party library

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

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

Java

Triggers

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

key based and custom

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Asynchronous and synchronous physical replication; geographically distributed replicas; support for object storages.

none

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

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

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

but no files for transaction logging

optimistic locking

configurable

ACID within a storage node (=shard)

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

Snapshots and command logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

off heap cache

User concepts

Access control

Access rights for users and roles. Column and row based policies. Quotas and resource limits. Pluggable authentication with LDAP and Kerberos. Password based, X.509 certificate, and SSH key authentication.

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

Access rights based on private key authentication or shared access signatures

Access rights for users and roles

Users and roles with access to stored procedures

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.