DBMS > Amazon Redshift vs. Microsoft Access vs. Rockset vs. TerminusDB

System Properties Comparison Amazon Redshift vs. Microsoft Access vs. Rockset vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

A scalable, reliable search and analytics service in the cloud, built on RocksDB

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

Primary database model

Relational DBMS

Document store

Graph DBMS

Secondary database models

Relational DBMS
Search engine

Document store
RDF store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	0.82
Rank	#212	Overall
	#36	Document stores

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

aws.amazon.com/redshift

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

rockset.com

terminusdb.com

Technical documentation

docs.aws.amazon.com/redshift

developer.microsoft.com/en-us/access

docs.rockset.com

terminusdb.github.io/terminusdb/#

Developer

Amazon (based on PostgreSQL)

Microsoft

Rockset

DataChemist Ltd.

Initial release

2012

1992

2019

2018

Current release

1902 (16.0.11328.20222), March 2019

11.0.0, January 2023

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

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

hosted

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

dynamic typing

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.

ingestion from XML files supported

Secondary indexes

restricted

yes

all fields are automatically indexed

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

but not compliant to any SQL standard

Read-only SQL queries, including JOINs

SQL-like query language (WOQL)

APIs and other access methods

JDBC
ODBC

ADO.NET
DAO
ODBC
OLE DB

HTTP REST

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

All languages supporting JDBC/ODBC

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

Go
Java
JavaScript (Node.js)
Python

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

since Access 2010 using the ACE-engine

yes

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Automatic sharding

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

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 journaling

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 for users and organizations can be defined via Rockset console

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.