DBMS > Kinetica vs. RavenDB vs. SAP HANA vs. SAP SQL Anywhere

System Properties Comparison Kinetica vs. RavenDB vs. SAP HANA vs. SAP SQL Anywhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fully vectorized database across both GPUs and CPUs

Open Source Operational and Transactional Enterprise NoSQL Document Database

In-memory, column based data store. Available as appliance or cloud service

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

www.kinetica.com

ravendb.net

www.sap.com/products/hana.html

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

docs.kinetica.com

ravendb.net/docs

help.sap.com/hana

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Kinetica

Hibernating Rhinos

SAP

formerly Sybase

Initial release

2012

2010

1992

Current release

7.1, August 2021

5.4, July 2022

2.0 SPS07 (April 4, 2023), April 2023

17, July 2015

License

Commercial or Open Source

commercial

Open Source

AGPL version 3, commercial license available

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C, C++

Server operating systems

Linux

Linux
macOS
Raspberry Pi
Windows

Appliance or cloud-service

AIX
HP-UX
Linux
OS X
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

SQL-like query language (RQL)

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

JDBC
ODBC

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

C++
Java
JavaScript (Node.js)
Python

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

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

SQLScript, R

yes, in C/C++, Java, .Net or Perl

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

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

yes

Source-replica replication

Database mirroring

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

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

User concepts

Access control

Access rights for users and roles on table level

Authorization levels configured per client per database

yes

fine grained access rights according to SQL-standard

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.