DBMS > Amazon Redshift vs. EXASOL vs. Hive vs. Microsoft Access vs. TigerGraph

System Properties Comparison Amazon Redshift vs. EXASOL vs. Hive vs. Microsoft Access vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

data warehouse software for querying and managing large distributed datasets, built on Hadoop

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 complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Relational DBMS

Graph DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	59.76
Rank	#18	Overall
	#12	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

aws.amazon.com/redshift

www.exasol.com

hive.apache.org

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

www.tigergraph.com

Technical documentation

docs.aws.amazon.com/redshift

www.exasol.com/resources

cwiki.apache.org/confluence/display/Hive/Home

developer.microsoft.com/en-us/access

docs.tigergraph.com

Developer

Amazon (based on PostgreSQL)

Exasol

Apache Software Foundation

initially developed by Facebook

Microsoft

Initial release

2012

2000

2012

1992

2017

Current release

3.1.3, April 2022

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

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

All OS with a Java VM

Windows

Not a real database server, but making use of DLLs

Linux

Data scheme

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

SQL-like DML and DDL statements

yes

but not compliant to any SQL standard

SQL-like query language (GSQL)

APIs and other access methods

JDBC
ODBC

.Net
JDBC
ODBC
WebSocket

JDBC
ODBC
Thrift

ADO.NET
DAO
ODBC
OLE DB

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

Java
Lua
Python
R

C++
Java
PHP
Python

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

C++
Java

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

user defined functions and integration of map-reduce

yes

since Access 2010 using the ACE-engine

yes

Triggers

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

query execution via MapReduce

yes

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

Relationships in graphs

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

Access rights for users, groups and roles according to SQL-standard

Access rights for users, groups and roles

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

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.