DBMS > Apache Drill vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. Riak TS vs. Stardog

System Properties Comparison Apache Drill vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. Riak TS vs. Stardog

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Primary database model

Document store
Relational DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Graph DBMS
RDF store

Secondary database models

Spatial DBMS

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational 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	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	2.07
Rank	#122	Overall
	#11	Graph DBMS
	#6	RDF stores

Website

drill.apache.org

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

azure.microsoft.com/services/cosmos-db

www.stardog.com

Technical documentation

drill.apache.org/docs

developer.microsoft.com/en-us/access

learn.microsoft.com/azure/cosmos-db

www.tiot.jp/riak-docs/riak/ts/latest

docs.stardog.com

Developer

Apache Software Foundation

Microsoft

Open Source, formerly Basho Technologies

Stardog-Union

Initial release

2012

1992

2014

2015

2010

Current release

1.20.3, January 2023

1902 (16.0.11328.20222), March 2019

3.0.0, September 2022

7.3.0, May 2020

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Bundled with Microsoft Office

commercial

Open Source

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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

Erlang

Java

Server operating systems

Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

hosted

Linux
OS X

Linux
macOS
Windows

Data scheme

schema-free

yes

schema-free

schema-free and OWL/RDFS-schema support

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.

Import/export of XML data possible

Secondary indexes

yes

All properties auto-indexed by default

restricted

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

but not compliant to any SQL standard

SQL-like query language

yes, limited

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

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

HTTP API
Native Erlang Interface

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Supported programming languages

C++

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

since Access 2010 using the ACE-engine

JavaScript

Erlang

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

yes

since Access 2010 using the ACE-engine

JavaScript

yes

pre-commit hooks and post-commit hooks

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service

selectable replication factor

Multi-source replication in HA-Cluster

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency

Immediate Consistency in HA-Cluster

Foreign keys

Referential integrity

yes

links between datasets can be stored

yes

relationships in graphs

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

Depending on the underlying data source

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.

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

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

Access rights can be defined down to the item level

Access rights for users and roles

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.