DBMS > Amazon Redshift vs. Atos Standard Common Repository vs. BigObject vs. Microsoft Access vs. OpenQM

System Properties Comparison Amazon Redshift vs. Atos Standard Common Repository vs. BigObject vs. Microsoft Access vs. OpenQM

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Analytic DBMS for real-time computations and queries

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

QpenQM is a high-performance, self-tuning, multi-value DBMS

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Multivalue DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Website

aws.amazon.com/redshift

atos.net/en/convergence-creators/portfolio/standard-common-repository

bigobject.io

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

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

Technical documentation

docs.aws.amazon.com/redshift

docs.bigobject.io

developer.microsoft.com/en-us/access

Developer

Amazon (based on PostgreSQL)

Atos Convergence Creators

BigObject, Inc.

Microsoft

Rocket Software, originally Martin Phillips

Initial release

2012

2016

2015

1992

1993

Current release

1703

1902 (16.0.11328.20222), March 2019

3.4-12

License

Commercial or Open Source

commercial

free community edition available

commercial

Bundled with Microsoft Office

Open Source

GPLv2, extended commercial license available

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

Java

C++

Server operating systems

hosted

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Windows

Not a real database server, but making use of DLLs

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Data scheme

yes

Schema and schema-less with LDAP views

yes

with some exceptions

Typing

predefined data types such as float or date

yes

optional

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

yes

but not compliant to any SQL standard

APIs and other access methods

JDBC
ODBC

LDAP

fluentd
ODBC
RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

Supported programming languages

All languages supporting JDBC/ODBC

All languages with LDAP bindings

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

.Net
Basic
C
Java
Objective C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

Lua

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

cell division

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

none

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Durability

Support for making data persistent

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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

LDAP bind authentication

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

Access rights can be defined down to the item level

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.