DBMS > SAP HANA vs. SAP SQL Anywhere vs. SQL.JS vs. VoltDB vs. Yanza

System Properties Comparison SAP HANA vs. SAP SQL Anywhere vs. SQL.JS vs. VoltDB vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Port of SQLite to JavaScript

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

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Score	0.63
Rank	#241	Overall
	#112	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

www.sap.com/products/hana.html

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

sql.js.org

www.voltdb.com

yanza.com

Technical documentation

help.sap.com/hana

help.sap.com/docs/SAP_SQL_Anywhere

sql.js.org/documentation/index.html

docs.voltdb.com

Developer

SAP

formerly Sybase

Alon Zakai

enhancements implemented by others

VoltDB Inc.

Yanza

Initial release

2010

1992

2012

2010

2015

Current release

2.0 SPS07 (April 4, 2023), April 2023

17, July 2015

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

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

commercial

free version available

Cloud-based only

Only available as a cloud service

also available as a cloud based service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

JavaScript

Java, C++

Server operating systems

Appliance or cloud-service

AIX
HP-UX
Linux
OS X
Solaris
Windows

server-less, requires a JavaScript environment (browser, Node.js)

Linux
OS X

for development

Windows

Data scheme

yes

schema-free

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-92 is not fully supported

yes

only a subset of SQL 99

APIs and other access methods

JDBC
ODBC

ADO.NET
HTTP API
JDBC
ODBC

JavaScript API

Java API
JDBC
RESTful HTTP/JSON API

HTTP API

Supported programming languages

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

JavaScript

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

SQLScript, R

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

Java

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

yes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Database mirroring

none

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate 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

yes

Durability

Support for making data persistent

yes

except by serializing a db to a file

yes

Snapshots and command logging

yes

In-memory capabilities

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

yes

User concepts

Access control

yes

fine grained access rights according to SQL-standard

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.