DBMS > Amazon Redshift vs. CockroachDB vs. Microsoft Access vs. VoltDB

System Properties Comparison Amazon Redshift vs. CockroachDB vs. Microsoft Access vs. VoltDB

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

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

aws.amazon.com/redshift

www.cockroachlabs.com

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

www.voltdb.com

Technical documentation

docs.aws.amazon.com/redshift

www.cockroachlabs.com/docs

developer.microsoft.com/en-us/access

docs.voltdb.com

Developer

Amazon (based on PostgreSQL)

Cockroach Labs

Microsoft

VoltDB Inc.

Initial release

2012

2015

1992

2010

Current release

23.1.1, May 2023

1902 (16.0.11328.20222), March 2019

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0, commercial license available

commercial

Bundled with Microsoft Office

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, C++

Server operating systems

hosted

Linux
macOS
Windows

Windows

Not a real database server, but making use of DLLs

Linux
OS X

for development

Data scheme

yes

dynamic schema

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes, wire compatible with PostgreSQL

yes

but not compliant to any SQL standard

yes

only a subset of SQL 99

APIs and other access methods

JDBC
ODBC

JDBC

ADO.NET
DAO
ODBC
OLE DB

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

since Access 2010 using the ACE-engine

Java

Triggers

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using RAFT

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

FOREIGN KEY constraints are not supported

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

but no files for transaction logging

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

Snapshots and command logging

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

Role-based access control

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

Users and roles with access to stored procedures

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.