DBMS > Microsoft Access vs. RavenDB vs. Snowflake vs. TerminusDB

System Properties Comparison Microsoft Access vs. RavenDB vs. Snowflake vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

Cloud-based data warehousing service for structured and semi-structured data

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
RDF store

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

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

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

ravendb.net

www.snowflake.com

terminusdb.com

Technical documentation

developer.microsoft.com/en-us/access

ravendb.net/docs

docs.snowflake.net/manuals/index.html

terminusdb.github.io/terminusdb/#

Developer

Microsoft

Hibernating Rhinos

Snowflake Computing Inc.

DataChemist Ltd.

Initial release

1992

2010

2014

2018

Current release

1902 (16.0.11328.20222), March 2019

5.4, July 2022

11.0.0, January 2023

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

AGPL version 3, commercial license available

commercial

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

Windows

Not a real database server, but making use of DLLs

Linux
macOS
Raspberry Pi
Windows

hosted

Linux

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like query language (RQL)

yes

SQL-like query language (WOQL)

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

CLI Client
JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

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

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript (Node.js)
Python

JavaScript
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

yes

user defined functions

yes

Triggers

yes

since Access 2010 using the ACE-engine

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

yes

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

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, Cluster-wide transaction available

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 journaling

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

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

Authorization levels configured per client per database

Users with fine-grained authorization concept, user roles and pluggable authentication

Role-based access control

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.