DBMS > ClickHouse vs. Hawkular Metrics vs. Microsoft Access vs. Oracle Berkeley DB vs. SAP SQL Anywhere

System Properties Comparison ClickHouse vs. Hawkular Metrics vs. Microsoft Access vs. Oracle Berkeley DB 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.

Hawkular metrics is the metric storage of the Red Hat sponsored Hawkular monitoring system. It is based on Cassandra.

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 in-process key-value store

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

Primary database model

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

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	0.00
Rank	#379	Overall
	#40	Time Series DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

clickhouse.com

www.hawkular.org

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

www.oracle.com/database/technologies/related/berkeleydb.html

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

Technical documentation

clickhouse.com/docs

www.hawkular.org/hawkular-metrics/docs/user-guide

developer.microsoft.com/en-us/access

docs.oracle.com/cd/E17076_05/html/index.html

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Clickhouse Inc.

Community supported by Red Hat

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

SAP

formerly Sybase

Initial release

2016

2014

1992

1994

1992

Current release

v24.4.1.2088-stable, May 2024

1902 (16.0.11328.20222), March 2019

18.1.40, May 2020

17, July 2015

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

Open Source

commercial license available

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.
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.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.

Implementation language

C++

Java

C++

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

FreeBSD
Linux
macOS

Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

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

only with the Berkeley DB XML edition

yes

Secondary indexes

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

yes

but not compliant to any SQL standard

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

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

HTTP REST

ADO.NET
DAO
ODBC
OLE DB

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

Go
Java
Python
Ruby

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

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

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

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

Triggers

yes

via Hawkular Alerting

yes

since Access 2010 using the ACE-engine

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

key based and custom

Sharding

based on Cassandra

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

selectable replication factor

based on Cassandra

none

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate 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

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

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

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.