DBMS > Kinetica vs. Machbase Neo vs. Microsoft SQL Server vs. Qdrant vs. VoltDB

System Properties Comparison Kinetica vs. Machbase Neo vs. Microsoft SQL Server vs. Qdrant vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

Fully vectorized database across both GPUs and CPUs

TimeSeries DBMS for AIoT and BigData

Microsofts flagship relational DBMS

A high-performance vector database with neural network or semantic-based matching

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

Spatial DBMS
Time Series DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

www.kinetica.com

machbase.com

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

github.com/qdrant/qdrant
qdrant.tech

www.voltdb.com

Technical documentation

docs.kinetica.com

machbase.com/dbms

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

qdrant.tech/documentation

docs.voltdb.com

Developer

Kinetica

Machbase

Microsoft

Qdrant

VoltDB Inc.

Initial release

2012

2013

1989

2021

2010

Current release

7.1, August 2021

V8.0, August 2023

SQL Server 2022, November 2022

11.3, April 2022

License

Commercial or Open Source

commercial

free test version available

commercial

restricted free version is available

Open Source

Apache Version 2.0

Open Source

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

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

Rust

Java, C++

Server operating systems

Linux

Linux
macOS
Windows

Linux
Windows

Docker
Linux
macOS
Windows

Linux
OS X

for development

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language

yes

only a subset of SQL 99

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

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

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C++
Java
JavaScript (Node.js)
Python

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

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

Java

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

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

yes, but depending on the SQL-Server Edition

Collection-level replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency, tunable 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

GPU vRAM or System RAM

yes

volatile and lookup table

yes

User concepts

Access control

Access rights for users and roles on table level

simple password-based access control

fine grained access rights according to SQL-standard

Key-based authentication

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.