DBMS > EsgynDB vs. Ingres vs. SAP HANA vs. VictoriaMetrics

System Properties Comparison EsgynDB vs. Ingres vs. SAP HANA vs. VictoriaMetrics

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Well established RDBMS

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

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

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	0.15
Rank	#325	Overall
	#144	Relational DBMS

Score	3.63
Rank	#79	Overall
	#43	Relational DBMS

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Score	1.23
Rank	#165	Overall
	#15	Time Series DBMS

Website

www.esgyn.cn

www.actian.com/databases/ingres

www.sap.com/products/hana.html

victoriametrics.com

Technical documentation

docs.actian.com/ingres

help.sap.com/hana

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

Esgyn

Actian Corporation

SAP

VictoriaMetrics

Initial release

2015

1974

originally developed at University Berkely in early 1970s

2010

2018

Current release

12.0, July 2024

2.0 SPS07 (April 4, 2023), April 2023

v1.91, May 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

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

Server operating systems

Linux

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Appliance or cloud-service

FreeBSD
Linux
macOS
OpenBSD

Data scheme

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.

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

JDBC
ODBC

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

Java Stored Procedures

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Ingres Replicator

yes

Synchronous replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual 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

MVCC

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

User concepts

Access control

fine grained access rights according to SQL-standard

yes

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.