DBMS > Amazon Redshift vs. Kinetica vs. Linter vs. Microsoft Azure SQL Database vs. Qdrant

System Properties Comparison Amazon Redshift vs. Kinetica vs. Linter vs. Microsoft Azure SQL Database vs. Qdrant

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Fully vectorized database across both GPUs and CPUs

RDBMS for high security requirements

Database as a Service offering with high compatibility to Microsoft SQL Server

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

Primary database model

Relational DBMS

Vector DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Website

aws.amazon.com/redshift

www.kinetica.com

linter.ru

azure.microsoft.com/en-us/products/azure-sql/database

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

docs.aws.amazon.com/redshift

docs.kinetica.com

docs.microsoft.com/en-us/azure/azure-sql

qdrant.tech/documentation

Developer

Amazon (based on PostgreSQL)

Kinetica

relex.ru

Microsoft

Qdrant

Initial release

2012

1990

2010

2021

Current release

7.1, August 2021

V12

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

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

C, C++

C and C++

C++

Rust

Server operating systems

hosted

Linux

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

hosted

Docker
Linux
macOS
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

restricted

yes

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

ADO.NET
JDBC
ODBC

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Supported programming languages

All languages supporting JDBC/ODBC

C++
Java
JavaScript (Node.js)
Python

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

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

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

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

proprietary syntax with the possibility to convert from PL/SQL

Transact SQL

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

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes, with always 3 replicas available

Collection-level replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency, tunable consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

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

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles on table level

fine grained access rights according to SQL-standard

Key-based authentication

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.