DBMS > Amazon Aurora vs. Apache Impala vs. Dolt vs. Microsoft SQL Server vs. Sqrrl

System Properties Comparison Amazon Aurora vs. Apache Impala vs. Dolt vs. Microsoft SQL Server vs. Sqrrl

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Description

MySQL and PostgreSQL compatible cloud service by Amazon

Analytic DBMS for Hadoop

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

Microsofts flagship relational DBMS

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Document store

Document store
Graph DBMS
Spatial DBMS

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

Score	7.91
Rank	#50	Overall
	#32	Relational DBMS

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

aws.amazon.com/rds/aurora

impala.apache.org

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

www.microsoft.com/en-us/sql-server

sqrrl.com

Technical documentation

docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Aurora.html

impala.apache.org/impala-docs.html

docs.dolthub.com

learn.microsoft.com/en-US/sql/sql-server

Developer

Amazon

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

DoltHub Inc

Microsoft

Amazon

originally Sqrrl Data, Inc.

Initial release

2015

2013

2018

1989

2012

Current release

4.1.0, June 2022

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

Apache Version 2.0

commercial

restricted free version is available

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

Java

Server operating systems

hosted

Linux

Linux
macOS
Windows

Linux
Windows

Linux

Data scheme

yes

schema-free

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

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC

CLI Client
HTTP REST

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Supported programming languages

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

All languages supporting JDBC/ODBC

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

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

currently in alpha release

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

none

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

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

yes, but depending on the SQL-Server Edition

selectable replication factor

making use of Hadoop

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic updates per row, document, or graph entity

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

based on Apache Sentry and Kerberos

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

fine grained access rights according to SQL-standard

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.