DBMS > Graph Engine vs. Ingres vs. SAP HANA vs. VelocityDB

System Properties Comparison Graph Engine vs. Ingres vs. SAP HANA vs. VelocityDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Well established RDBMS

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

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Graph DBMS
Key-value store

Relational DBMS

Graph DBMS
Object oriented 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.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	3.80
Rank	#82	Overall
	#44	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.11
Rank	#354	Overall
	#37	Graph DBMS
	#15	Object oriented DBMS

Website

www.graphengine.io

www.actian.com/databases/ingres

www.sap.com/products/hana.html

velocitydb.com

Technical documentation

www.graphengine.io/docs/manual

docs.actian.com/ingres

help.sap.com/hana

velocitydb.com/UserGuide

Developer

Microsoft

Actian Corporation

SAP

VelocityDB Inc

Initial release

2010

1974

originally developed at University Berkely in early 1970s

2010

2011

Current release

11.2, May 2022

2.0 SPS07 (April 4, 2023), April 2023

7.x

License

Commercial or Open Source

Open Source

MIT License

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

.NET and C

Server operating systems

.NET

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Appliance or cloud-service

Any that supports .NET

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

RESTful HTTP API

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

JDBC
ODBC

.Net

Supported programming languages

C#
C++
F#
Visual Basic

.Net

Server-side scripts

Stored procedures

yes

SQLScript, R

Triggers

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Ingres Star to access multiple databases simultaneously

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Ingres Replicator

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

MVCC

yes

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

Based on Windows 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.