DBMS > Machbase Neo vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. TimescaleDB

System Properties Comparison Machbase Neo vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. TimescaleDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

TimeSeries DBMS for AIoT and BigData

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

Globally distributed, horizontally scalable, multi-model database service

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

Primary database model

Time Series DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Spatial DBMS

Relational DBMS

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

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

machbase.com

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

azure.microsoft.com/services/cosmos-db

www.timescale.com

Technical documentation

machbase.com/dbms

developer.microsoft.com/en-us/access

learn.microsoft.com/azure/cosmos-db

docs.timescale.com

Developer

Machbase

Microsoft

Timescale

Initial release

2013

1992

2014

2017

Current release

V8.0, August 2023

1902 (16.0.11328.20222), March 2019

2.15.0, May 2024

License

Commercial or Open Source

commercial

free test version available

commercial

Bundled with Microsoft Office

commercial

Open Source

Apache 2.0

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.

Implementation language

C++

Server operating systems

Linux
macOS
Windows

Windows

Not a real database server, but making use of DLLs

hosted

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

but not compliant to any SQL standard

SQL-like query language

yes

full PostgreSQL SQL syntax

APIs and other access methods

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

ADO.NET
DAO
ODBC
OLE DB

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

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

Supported programming languages

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

JavaScript

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

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

yes

Implicit feature of the cloud service

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session 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

Multi-item ACID transactions with snapshot isolation within a partition

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

volatile and lookup table

User concepts

Access control

simple password-based access control

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

Access rights can be defined down to the item level

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.