DBMS > ClickHouse vs. Interbase vs. KeyDB vs. Microsoft Access vs. Microsoft Azure Synapse Analytics

System Properties Comparison ClickHouse vs. Interbase vs. KeyDB vs. Microsoft Access vs. Microsoft Azure Synapse Analytics

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.

Light-weight proven RDBMS

originally from Borland

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

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

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

Primary database model

Relational DBMS

Key-value store

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	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	19.93
Rank	#31	Overall
	#19	Relational DBMS

Website

clickhouse.com

www.embarcadero.com/products/interbase

github.com/Snapchat/KeyDB
keydb.dev

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

azure.microsoft.com/services/synapse-analytics

Technical documentation

clickhouse.com/docs

docs.embarcadero.com/products/interbase

docs.keydb.dev

developer.microsoft.com/en-us/access

docs.microsoft.com/azure/synapse-analytics

Developer

Clickhouse Inc.

Embarcadero

EQ Alpha Technology Ltd.

Microsoft

Initial release

2016

1984

2019

1992

2016

Current release

v24.4.1.2088-stable, May 2024

InterBase 2020, December 2019

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

BSD-3

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.

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++

Server operating systems

FreeBSD
Linux
macOS

Android
iOS
Linux
OS X
Windows

Linux

Windows

Not a real database server, but making use of DLLs

hosted

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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.

export as XML data possible

Secondary indexes

yes

by using the Redis Search module

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

yes

but not compliant to any SQL standard

yes

APIs and other access methods

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

ADO.NET
JDBC
ODBC

Proprietary protocol

RESP - REdis Serialization Protoco

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
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

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

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

C#
Java
PHP

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

Lua

yes

since Access 2010 using the ACE-engine

Transact SQL

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

none

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

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

Interbase Change Views

Multi-source replication
Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Foreign keys

Referential integrity

yes

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

Transaction concepts

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

ACID

Optimistic locking, atomic execution of commands blocks and scripts

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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.

fine grained access rights according to SQL-standard

simple password-based access control and ACL

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

yes

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.