DBMS > Microsoft SQL Server vs. OpenTSDB vs. Tarantool vs. Tkrzw

System Properties Comparison Microsoft SQL Server vs. OpenTSDB vs. Tarantool vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Microsofts flagship relational DBMS

Scalable Time Series DBMS based on HBase

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS

Time Series DBMS

Document store
Key-value store
Relational DBMS

Key-value store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.68
Rank	#146	Overall
	#12	Time Series DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

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

opentsdb.net

www.tarantool.io

dbmx.net/tkrzw

Technical documentation

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

opentsdb.net/docs/build/html/index.html

www.tarantool.io/en/doc

Developer

Microsoft

currently maintained by Yahoo and other contributors

Mikio Hirabayashi

Initial release

1989

2011

2008

2020

Current release

SQL Server 2022, November 2022

2.10.0, May 2022

0.9.3, August 2020

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

LGPL

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

Open Source

Apache Version 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.

Implementation language

C++

Java

C and C++

C++

Server operating systems

Linux
Windows

BSD
Linux
macOS

Linux
macOS

Data scheme

yes

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

schema-free

Typing

predefined data types such as float or date

yes

numeric data for metrics, strings for tags

string, double, decimal, uuid, integer, blob, boolean, datetime

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

Full-featured ANSI SQL support

APIs and other access methods

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

HTTP API
Telnet API

Open binary protocol

Supported programming languages

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

Erlang
Go
Java
Python
R
Ruby

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

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

Lua, C and SQL stored procedures

Triggers

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

based on HBase

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, but depending on the SQL-Server Edition

selectable replication factor

based on HBase

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

none

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

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

yes, write ahead logging

yes

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

yes

using specific database classes

User concepts

Access control

fine grained access rights according to SQL-standard

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.