DBMS > Amazon Redshift vs. Apache Drill vs. Dolt vs. Linter vs. Microsoft Azure SQL Database

System Properties Comparison Amazon Redshift vs. Apache Drill vs. Dolt 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

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

A MySQL compatible DBMS with Git-like versioning of data and schema

RDBMS for high security requirements

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

Primary database model

Relational DBMS

Document store
Relational DBMS

Relational DBMS

Secondary database models

Document store

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Website

aws.amazon.com/redshift

drill.apache.org

github.com/dolthub/dolt
www.dolthub.com

linter.ru

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

Technical documentation

docs.aws.amazon.com/redshift

drill.apache.org/docs

docs.dolthub.com

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

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

DoltHub Inc

relex.ru

Microsoft

Initial release

2012

2018

1990

2010

Current release

1.20.3, January 2023

V12

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

Apache Version 2.0

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

Linux
OS X
Windows

Linux
macOS
Windows

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

SQL SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

CLI Client
HTTP REST

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

ADO.NET
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

C++

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

currently in alpha release

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

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Source-replica replication

yes, with always 3 replicas available

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Depending on the underlying data source

User concepts

Access control

fine grained access rights according to SQL-standard

Depending on the underlying data source

Only one user is configurable, and must be specified in the config file at startup

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.