DBMS > HEAVY.AI vs. Microsoft SQL Server vs. Riak KV vs. SWC-DB

System Properties Comparison HEAVY.AI vs. Microsoft SQL Server vs. Riak KV vs. SWC-DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Microsofts flagship relational DBMS

Distributed, fault tolerant key-value store

A high performance, scalable Wide Column DBMS

Primary database model

Relational DBMS

Key-value store

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

Wide column store

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

Time Series DBMS

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

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

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

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

github.com/heavyai/heavydb
www.heavy.ai

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

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

docs.heavy.ai

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

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

Developer

HEAVY.AI, Inc.

Microsoft

OpenSource, formerly Basho Technologies

Alex Kashirin

Initial release

2016

1989

2009

2020

Current release

5.10, January 2022

SQL Server 2022, November 2022

3.2.0, December 2022

0.5, April 2021

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

commercial

restricted free version is available

Open Source

Apache version 2, commercial enterprise edition

Open Source

GPL V3

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

C++

Erlang

C++

Server operating systems

Linux

Linux
Windows

Linux
OS X

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

yes

SQL-like query language

APIs and other access methods

JDBC
ODBC
Thrift
Vega

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

HTTP API
Native Erlang Interface

Proprietary protocol
Thrift

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
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++

Server-side scripts

Stored procedures

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

Round robin

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

Multi-source replication

yes, but depending on the SQL-Server Edition

selectable replication factor

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

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

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.