DBMS > Apache IoTDB vs. HBase vs. Microsoft SQL Server vs. Sadas Engine

System Properties Comparison Apache IoTDB vs. HBase vs. Microsoft SQL Server vs. Sadas Engine

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

Wide-column store based on Apache Hadoop and on concepts of BigTable

Microsofts flagship relational DBMS

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

Time Series DBMS

Wide column store

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.18
Rank	#173	Overall
	#15	Time Series DBMS

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Website

iotdb.apache.org

hbase.apache.org

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

www.sadasengine.com

Technical documentation

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

hbase.apache.org/book.html

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

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Microsoft

SADAS s.r.l.

Initial release

2018

2008

1989

2006

Current release

1.1.0, April 2023

2.3.4, January 2021

SQL Server 2022, November 2022

8.0

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache version 2

commercial

restricted free version is available

commercial

free trial version available

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

Java

C++

Server operating systems

All OS with a Java VM (>= 1.8)

Linux
Unix
Windows

using Cygwin

Linux
Windows

AIX
Linux
Windows

Data scheme

yes

schema-free, schema definition possible

yes

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

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

SQL-like query language

yes

APIs and other access methods

JDBC
Native API

Java API
RESTful HTTP API
Thrift

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

JDBC
ODBC
Proprietary protocol

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

C
C#
C++
Groovy
Java
PHP
Python
Scala

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

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

yes

Coprocessors in Java

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

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

horizontal partitioning

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

Multi-source replication
Source-replica replication

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Single row ACID (across millions of columns)

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

managed by 'Learn by Usage'

User concepts

Access control

yes

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

fine grained access rights according to SQL-standard

Access rights for users, groups and roles according to SQL-standard

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.