DBMS > Graph Engine vs. Microsoft SQL Server vs. OpenQM vs. Riak KV

System Properties Comparison Graph Engine vs. Microsoft SQL Server vs. OpenQM vs. Riak KV

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Microsofts flagship relational DBMS

QpenQM is a high-performance, self-tuning, multi-value DBMS

Distributed, fault tolerant key-value store

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Multivalue DBMS

Key-value store

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

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.62
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	0.33
Rank	#286	Overall
	#10	Multivalue DBMS

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Website

www.graphengine.io

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

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

Technical documentation

www.graphengine.io/docs/manual

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

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

Developer

Microsoft

Rocket Software, originally Martin Phillips

OpenSource, formerly Basho Technologies

Initial release

2010

1989

1993

2009

Current release

SQL Server 2022, November 2022

3.4-12

3.2.0, December 2022

License

Commercial or Open Source

Open Source

MIT License

commercial

restricted free version is available

Open Source

GPLv2, extended commercial license available

Open Source

Apache version 2, commercial enterprise edition

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.

Implementation language

.NET and C

C++

Erlang

Server operating systems

.NET

Linux
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
OS X

Data scheme

yes

with some exceptions

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

APIs and other access methods

RESTful HTTP API

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

HTTP API
Native Erlang Interface

Supported programming languages

C#
C++
F#
Visual Basic

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

.Net
Basic
C
Java
Objective C
PHP
Python

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

Server-side scripts

Stored procedures

yes

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

yes

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

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

yes

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes, but depending on the SQL-Server Edition

yes

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

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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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 can be defined down to the item level

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.