DBMS > Microsoft SQL Server vs. OpenQM vs. TerminusDB vs. Warp 10

System Properties Comparison Microsoft SQL Server vs. OpenQM vs. TerminusDB vs. Warp 10

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Microsofts flagship relational DBMS

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
RDF store

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

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

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

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

terminusdb.com

www.warp10.io

Technical documentation

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

terminusdb.github.io/terminusdb/#

www.warp10.io/content/02_Getting_started

Developer

Microsoft

Rocket Software, originally Martin Phillips

DataChemist Ltd.

SenX

Initial release

1989

1993

2018

2015

Current release

SQL Server 2022, November 2022

3.4-12

11.0.0, January 2023

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

GPLv2, extended commercial license available

Open Source

GPL V3

Open Source

Apache License 2.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++

Prolog, Rust

Java

Server operating systems

Linux
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux

Linux
OS X
Windows

Data scheme

yes

with some exceptions

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 query language (WOQL)

APIs and other access methods

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

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

HTTP API
Jupyter
WebSocket

Supported programming languages

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

.Net
Basic
C
Java
Objective C
PHP
Python

JavaScript
Python

Server-side scripts

Stored procedures

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

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

yes

Graph Partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes, but depending on the SQL-Server Edition

yes

Journaling Streams

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

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 journaling

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

Role-based access control

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.