DBMS > Apache Impala vs. Microsoft SQL Server vs. Riak TS vs. YottaDB

System Properties Comparison Apache Impala vs. Microsoft SQL Server vs. Riak TS vs. YottaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Microsofts flagship relational DBMS

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

A fast and solid embedded Key-value store

Primary database model

Relational DBMS

Time Series DBMS

Key-value store

Secondary database models

Document store

Document store
Graph DBMS
Spatial DBMS

Relational DBMS

using the Octo plugin

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

Score	10.63
Rank	#40	Overall
	#24	Relational DBMS

Score	807.76
Rank	#3	Overall
	#3	Relational DBMS

Score	0.17
Rank	#318	Overall
	#27	Time Series DBMS

Score	0.21
Rank	#309	Overall
	#43	Key-value stores

Website

impala.apache.org

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

yottadb.com

Technical documentation

impala.apache.org/impala-docs.html

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

www.tiot.jp/riak-docs/riak/ts/latest

yottadb.com/resources/documentation

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Microsoft

Open Source, formerly Basho Technologies

YottaDB, LLC

Initial release

2013

1989

2015

2001

Current release

4.1.0, June 2022

SQL Server 2022, November 2022

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

restricted free version is available

Open Source

AGPL 3.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

C++

Erlang

Server operating systems

Linux

Linux
Windows

Linux
OS X

Docker
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

restricted

SQL

Support of SQL

SQL-like DML and DDL statements

yes

yes, limited

by using the Octo plugin

APIs and other access methods

JDBC
ODBC

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

HTTP API
Native Erlang Interface

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

All languages supporting JDBC/ODBC

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

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

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes, but depending on the SQL-Server Edition

selectable replication factor

yes

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

Eventual Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

Transaction concepts

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

ACID

optimistic locking

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

fine grained access rights according to SQL-standard

Users and groups based on OS-security mechanisms

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.