DBMS > Citus vs. Microsoft Access vs. SAP HANA vs. TimescaleDB

System Properties Comparison Citus vs. Microsoft Access vs. SAP HANA vs. TimescaleDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

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

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

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Relational DBMS

Time Series DBMS

Secondary database models

Document store

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Relational DBMS

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

Score	2.15
Rank	#117	Overall
	#56	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

www.citusdata.com

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

www.sap.com/products/hana.html

www.timescale.com

Technical documentation

docs.citusdata.com

developer.microsoft.com/en-us/access

help.sap.com/hana

docs.timescale.com

Developer

Microsoft

SAP

Timescale

Initial release

2010

1992

2010

2017

Current release

8.1, December 2018

1902 (16.0.11328.20222), March 2019

2.0 SPS07 (April 4, 2023), April 2023

2.15.0, May 2024

License

Commercial or Open Source

Open Source

AGPL, commercial license also available

commercial

Bundled with Microsoft Office

commercial

Open Source

Apache 2.0

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

C++

Server operating systems

Linux

Windows

Not a real database server, but making use of DLLs

Appliance or cloud-service

Linux
OS X
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

specific XML type available, but no XML query functionality

yes

Secondary indexes

yes

SQL

Support of SQL

yes

standard, with numerous extensions

yes

but not compliant to any SQL standard

yes

full PostgreSQL SQL syntax

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

ADO.NET
DAO
ODBC
OLE DB

JDBC
ODBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

yes

since Access 2010 using the ACE-engine

SQLScript, R

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

none

yes

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

fine grained access rights according to SQL-standard

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

yes

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.