DBMS > Microsoft SQL Server vs. mSQL vs. RavenDB vs. SiteWhere vs. XTDB

System Properties Comparison Microsoft SQL Server vs. mSQL vs. RavenDB vs. SiteWhere vs. XTDB

Editorial information provided by DB-Engines

Name

Description

Microsofts flagship relational DBMS

mSQL (Mini SQL) is a simple and lightweight RDBMS

Open Source Operational and Transactional Enterprise NoSQL Document Database

M2M integration platform for persisting/querying time series data

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	1.27
Rank	#169	Overall
	#76	Relational DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

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

hughestech.com.au/products/msql

ravendb.net

github.com/sitewhere/sitewhere

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

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

ravendb.net/docs

sitewhere1.sitewhere.io/index.html

www.xtdb.com/docs

Developer

Microsoft

Hughes Technologies

Hibernating Rhinos

SiteWhere

Juxt Ltd.

Initial release

1989

1994

2010

2019

Current release

SQL Server 2022, November 2022

4.4, October 2021

5.4, July 2022

1.19, September 2021

License

Commercial or Open Source

commercial

restricted free version is available

commercial

free licenses can be provided

Open Source

AGPL version 3, commercial license available

Open Source

Common Public Attribution License Version 1.0

Open Source

MIT License

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

Java

Clojure

Server operating systems

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
macOS
Raspberry Pi
Windows

Linux
OS X
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

predefined scheme

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

SQL-like query language (RQL)

limited SQL, making use of Apache Calcite

APIs and other access methods

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

JDBC
ODBC

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

HTTP REST

HTTP REST
JDBC

Supported programming languages

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

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Clojure
Java

Server-side scripts

Stored procedures

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

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

none

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, but depending on the SQL-Server Edition

none

Multi-source replication

selectable replication factor

based on HBase

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

Authorization levels configured per client per database

Users with fine-grained authorization concept

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.