DBMS > ClickHouse vs. Microsoft Access vs. Oracle NoSQL vs. Riak KV vs. SAP SQL Anywhere

System Properties Comparison ClickHouse vs. Microsoft Access vs. Oracle NoSQL vs. Riak KV vs. SAP SQL Anywhere

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 multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Distributed, fault tolerant key-value store

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Relational DBMS

Document store
Key-value store
Relational DBMS

Key-value store

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

Relational DBMS

Secondary database models

Time Series DBMS

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

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

clickhouse.com

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

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

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

clickhouse.com/docs

developer.microsoft.com/en-us/access

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

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

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Clickhouse Inc.

Microsoft

Oracle

OpenSource, formerly Basho Technologies

SAP

formerly Sybase

Initial release

2016

1992

2011

2009

1992

Current release

v24.4.1.2088-stable, May 2024

1902 (16.0.11328.20222), March 2019

23.3, December 2023

3.2.0, December 2022

17, July 2015

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

Open Source

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

Open Source

Apache version 2, commercial enterprise edition

commercial

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.

DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.
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

Erlang

Server operating systems

FreeBSD
Linux
macOS

Windows

Not a real database server, but making use of DLLs

Linux
Solaris SPARC/x86

Linux
OS X

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

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

schema-free

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.

yes

Secondary indexes

yes

restricted

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

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

HTTP API
Native Erlang Interface

ADO.NET
HTTP API
JDBC
ODBC

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

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

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

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

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

Erlang

yes, in C/C++, Java, .Net or Perl

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

key based and custom

none

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

none

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

selectable replication factor

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

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

ACID

but no files for transaction logging

configurable

ACID within a storage node (=shard)

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

off heap cache

yes

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 for users and roles

yes, using Riak Security

fine grained access rights according to SQL-standard

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.