DBMS > HEAVY.AI vs. Kinetica vs. Microsoft SQL Server vs. OpenQM

System Properties Comparison HEAVY.AI vs. Kinetica vs. Microsoft SQL Server vs. OpenQM

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Fully vectorized database across both GPUs and CPUs

Microsofts flagship relational DBMS

QpenQM is a high-performance, self-tuning, multi-value DBMS

Primary database model

Relational DBMS

Multivalue DBMS

Secondary database models

Spatial DBMS

Spatial DBMS
Time Series DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	2.10
Rank	#126	Overall
	#61	Relational DBMS

Score	0.69
Rank	#234	Overall
	#107	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	0.33
Rank	#286	Overall
	#10	Multivalue DBMS

Website

github.com/heavyai/heavydb
www.heavy.ai

www.kinetica.com

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

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

Technical documentation

docs.heavy.ai

docs.kinetica.com

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

Developer

HEAVY.AI, Inc.

Kinetica

Microsoft

Rocket Software, originally Martin Phillips

Initial release

2016

2012

1989

1993

Current release

5.10, January 2022

7.1, August 2021

SQL Server 2022, November 2022

3.4-12

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

commercial

restricted free version is available

Open Source

GPLv2, extended commercial license 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

C++ and CUDA

C, C++

C++

Server operating systems

Linux

Linux
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Data scheme

yes

with some exceptions

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

yes

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC
Thrift
Vega

JDBC
ODBC
RESTful HTTP API

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

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

C++
Java
JavaScript (Node.js)
Python

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

.Net
Basic
C
Java
Objective C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

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

yes

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

Round robin

Sharding

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

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

yes, but depending on the SQL-Server Edition

yes

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

Foreign keys

Referential integrity

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

Access rights can be defined down to the item level

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.