DBMS > Amazon Redshift vs. atoti vs. Coveo vs. Microsoft Access vs. SpaceTime

System Properties Comparison Amazon Redshift vs. atoti vs. Coveo vs. Microsoft Access vs. SpaceTime

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

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

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Secondary database models

Relational DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.61
Rank	#243	Overall
	#10	Object oriented DBMS

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	0.03
Rank	#392	Overall
	#8	Spatial DBMS

Website

aws.amazon.com/redshift

atoti.io

www.coveo.com

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

www.mireo.com/spacetime

Technical documentation

docs.aws.amazon.com/redshift

docs.atoti.io

docs.coveo.com

developer.microsoft.com/en-us/access

Developer

Amazon (based on PostgreSQL)

ActiveViam

Coveo

Microsoft

Mireo

Initial release

2012

1992

2020

Current release

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

free versions available

commercial

Bundled with Microsoft Office

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

Java

C++

Server operating systems

hosted

Windows

Not a real database server, but making use of DLLs

Linux

Data scheme

yes

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

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

Multidimensional Expressions (MDX)

yes

but not compliant to any SQL standard

A subset of ANSI SQL is implemented

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

C#
Java
JavaScript
Python

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

C#
C++
Python

Server-side scripts

Stored procedures

user defined functions

in Python

Python

yes

since Access 2010 using the ACE-engine

Triggers

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

yes

none

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Real-time block device replication (DRBD)

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

Transaction concepts

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

ACID

yes

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

granular access controls, API key management, content filters

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

yes

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.