DBMS > Apache IoTDB vs. Microsoft SQL Server vs. Rockset vs. VoltDB

System Properties Comparison Apache IoTDB vs. Microsoft SQL Server vs. Rockset vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

Microsofts flagship relational DBMS

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Relational DBMS
Search engine

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

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.79
Rank	#211	Overall
	#35	Document stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

iotdb.apache.org

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

rockset.com

www.voltdb.com

Technical documentation

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

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

docs.rockset.com

docs.voltdb.com

Developer

Apache Software Foundation

Microsoft

Rockset

VoltDB Inc.

Initial release

2018

1989

2019

2010

Current release

1.1.0, April 2023

SQL Server 2022, November 2022

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

restricted free version is available

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java

C++

Java, C++

Server operating systems

All OS with a Java VM (>= 1.8)

Linux
Windows

hosted

Linux
OS X

for development

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

dynamic typing

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

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

Read-only SQL queries, including JOINs

yes

only a subset of SQL 99

APIs and other access methods

JDBC
Native API

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

HTTP REST

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

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

Go
Java
JavaScript (Node.js)
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

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

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

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

Automatic sharding

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

yes, but depending on the SQL-Server Edition

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

yes

fine grained access rights according to SQL-standard

Access rights for users and organizations can be defined via Rockset console

Users and roles with access to stored procedures

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.