DBMS > Amazon Redshift vs. Microsoft Access vs. Riak KV vs. TimesTen

System Properties Comparison Amazon Redshift vs. Microsoft Access vs. Riak KV vs. TimesTen

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

Distributed, fault tolerant key-value store

In-Memory RDBMS compatible to Oracle

Primary database model

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

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	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	1.36
Rank	#161	Overall
	#75	Relational DBMS

Website

aws.amazon.com/redshift

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

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

docs.aws.amazon.com/redshift

developer.microsoft.com/en-us/access

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

docs.oracle.com/database/timesten-18.1

Developer

Amazon (based on PostgreSQL)

Microsoft

OpenSource, formerly Basho Technologies

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2012

1992

2009

1998

Current release

1902 (16.0.11328.20222), March 2019

3.2.0, December 2022

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

Server operating systems

hosted

Windows

Not a real database server, but making use of DLLs

Linux
OS X

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

yes

schema-free

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

but not compliant to any SQL standard

yes

APIs and other access methods

JDBC
ODBC

ADO.NET
DAO
ODBC
OLE DB

HTTP API
Native Erlang Interface

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

All languages supporting JDBC/ODBC

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

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

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

user defined functions

in Python

yes

since Access 2010 using the ACE-engine

Erlang

PL/SQL

Triggers

yes

since Access 2010 using the ACE-engine

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

selectable replication factor

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

links between data sets can be stored

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

by means of logfiles and checkpoints

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

yes, using Riak Security

fine grained access rights according to SQL-standard

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.