DBMS > KairosDB vs. Microsoft Access vs. Qdrant vs. SAP HANA

System Properties Comparison KairosDB vs. Microsoft Access vs. Qdrant vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed Time Series DBMS based on Cassandra or H2

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 high-performance vector database with neural network or semantic-based matching

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

github.com/kairosdb/kairosdb

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

github.com/qdrant/qdrant
qdrant.tech

www.sap.com/products/hana.html

Technical documentation

kairosdb.github.io

developer.microsoft.com/en-us/access

qdrant.tech/documentation

help.sap.com/hana

Developer

Microsoft

Qdrant

SAP

Initial release

2013

1992

2021

2010

Current release

1.2.2, November 2018

1902 (16.0.11328.20222), March 2019

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

Open Source

Apache Version 2.0

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C++

Rust

Server operating systems

Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

Docker
Linux
macOS
Windows

Appliance or cloud-service

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

APIs and other access methods

Graphite protocol
HTTP REST
Telnet API

ADO.NET
DAO
ODBC
OLE DB

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

JDBC
ODBC

Supported programming languages

Java
JavaScript

Node.js
PHP
Python

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

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

SQLScript, R

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

none

Collection-level replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency, tunable consistency

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

simple password-based access control

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

Key-based authentication

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.