DBMS > MaxDB vs. Microsoft SQL Server vs. Riak KV vs. TempoIQ vs. ToroDB

System Properties Comparison MaxDB vs. Microsoft SQL Server vs. Riak KV vs. TempoIQ vs. ToroDB

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A robust and reliable RDBMS optimized to run all major SAP solutions

Microsofts flagship relational DBMS

Distributed, fault tolerant key-value store

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Time Series DBMS

Document store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Website

maxdb.sap.com

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

tempoiq.com (offline)

github.com/torodb/server

Technical documentation

maxdb.sap.com/documentation

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

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

Developer

SAP, acquired from Software AG (Adabas-D) in 1997

Microsoft

OpenSource, formerly Basho Technologies

TempoIQ

8Kdata

Initial release

1984

1989

2009

2012

2016

Current release

7.9.10.12, February 2024

SQL Server 2022, November 2022

3.2.0, December 2022

License

Commercial or Open Source

commercial

Limited community edition free

commercial

restricted free version is available

Open Source

Apache version 2, commercial enterprise edition

commercial

Open Source

AGPL-V3

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

Erlang

Java

Server operating systems

AIX
HP-UX
Linux
Solaris
Windows

Linux
Windows

Linux
OS X

All OS with a Java 7 VM

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
WebDAV

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

HTTP API
Native Erlang Interface

HTTP API

Supported programming languages

.Net
C#
Java
Perl
PHP
Python

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#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

yes

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

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

none

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

Sharding

no "single point of failure"

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes, but depending on the SQL-Server Edition

selectable replication factor

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

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

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

yes, using Riak Security

simple authentication-based access control

Access rights for users and roles

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.