DBMS > Kinetica vs. Microsoft SQL Server vs. RavenDB vs. TerarkDB vs. Tibero

System Properties Comparison Kinetica vs. Microsoft SQL Server vs. RavenDB vs. TerarkDB vs. Tibero

Editorial information provided by DB-Engines

Name

Description

Fully vectorized database across both GPUs and CPUs

Microsofts flagship relational DBMS

Open Source Operational and Transactional Enterprise NoSQL Document Database

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Secondary database models

Spatial DBMS
Time Series DBMS

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	0.69
Rank	#234	Overall
	#107	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	3.01
Rank	#101	Overall
	#17	Document stores

Score	0.04
Rank	#377	Overall
	#58	Key-value stores

Score	1.81
Rank	#143	Overall
	#65	Relational DBMS

Website

www.kinetica.com

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

ravendb.net

github.com/bytedance/terarkdb

us.tmaxsoft.com/products/tibero

Technical documentation

docs.kinetica.com

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

ravendb.net/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Kinetica

Microsoft

Hibernating Rhinos

ByteDance, originally Terark

TmaxSoft

Initial release

2012

1989

2010

2016

2003

Current release

7.1, August 2021

SQL Server 2022, November 2022

5.4, July 2022

6, April 2015

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

AGPL version 3, commercial license available

commercial

restricted open source version available

commercial

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

C++

C and Assembler

Server operating systems

Linux

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free

yes

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

SQL-like DML and DDL statements

yes

SQL-like query language (RQL)

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

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

C++ API
Java API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

C++
Java
JavaScript (Node.js)
Python

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

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

C++
Java

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

user defined functions

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

yes

Persistent Stored Procedure (PSM)

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

none

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes, but depending on the SQL-Server Edition

Multi-source replication

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

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

In-memory capabilities

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

yes

GPU vRAM or System RAM

yes

planned for next version

User concepts

Access control

Access rights for users and roles on table level

fine grained access rights according to SQL-standard

Authorization levels configured per client per database

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.