DBMS > Amazon Redshift vs. EXASOL vs. Google Cloud Bigtable vs. Linter vs. Microsoft Azure SQL Database

System Properties Comparison Amazon Redshift vs. EXASOL vs. Google Cloud Bigtable vs. Linter vs. Microsoft Azure SQL Database

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.

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

RDBMS for high security requirements

Database as a Service offering with high compatibility to Microsoft SQL Server

Primary database model

Relational DBMS

Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial 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	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

Score	76.78
Rank	#16	Overall
	#11	Relational DBMS

Website

aws.amazon.com/redshift

www.exasol.com

cloud.google.com/bigtable

linter.ru

azure.microsoft.com/en-us/products/azure-sql/database

Technical documentation

docs.aws.amazon.com/redshift

www.exasol.com/resources

cloud.google.com/bigtable/docs

docs.microsoft.com/en-us/azure/azure-sql

Developer

Amazon (based on PostgreSQL)

Exasol

Google

relex.ru

Microsoft

Initial release

2012

2000

2015

1990

2010

Current release

V12

License

Commercial or Open Source

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

C++

Server operating systems

hosted

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

hosted

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.

yes

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

.Net
JDBC
ODBC
WebSocket

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

ADO.NET
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

Java
Lua
Python
R

C#
C++
Go
Java
JavaScript (Node.js)
Python

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

proprietary syntax with the possibility to convert from PL/SQL

Transact SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Internal replication in Colossus, and regional replication between two clusters in different zones

Source-replica replication

yes, with always 3 replicas available

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

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

Atomic single-row operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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 based on Google Cloud Identity and Access Management (IAM)

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.