DBMS > HEAVY.AI vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. SpaceTime

System Properties Comparison HEAVY.AI vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. SpaceTime

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

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

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Spatial DBMS

Secondary database models

Spatial DBMS

Relational DBMS

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

Score	2.10
Rank	#126	Overall
	#61	Relational DBMS

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

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

Score	0.00
Rank	#396	Overall
	#8	Spatial DBMS

Website

github.com/heavyai/heavydb
www.heavy.ai

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

azure.microsoft.com/services/cosmos-db

www.mireo.com/spacetime

Technical documentation

docs.heavy.ai

developer.microsoft.com/en-us/access

learn.microsoft.com/azure/cosmos-db

Developer

HEAVY.AI, Inc.

Microsoft

Mireo

Initial release

2016

1992

2014

2020

Current release

5.10, January 2022

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

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.

Implementation language

C++ and CUDA

C++

Server operating systems

Linux

Windows

Not a real database server, but making use of DLLs

hosted

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like query language

A subset of ANSI SQL is implemented

APIs and other access methods

JDBC
ODBC
Thrift
Vega

ADO.NET
DAO
ODBC
OLE DB

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

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

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

C#
C++
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

JavaScript

Triggers

yes

since Access 2010 using the ACE-engine

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

none

Sharding

Implicit feature of the cloud service

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

yes

Implicit feature of the cloud service

Real-time block device replication (DRBD)

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

Immediate Consistency

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

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

Access rights can be defined down to the item level

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.