DBMS > Google BigQuery vs. Graph Engine vs. Ingres vs. SAP HANA vs. YDB

System Properties Comparison Google BigQuery vs. Graph Engine vs. Ingres vs. SAP HANA vs. YDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

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 distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Relational DBMS

Document store
Relational 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	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.35
Rank	#278	Overall
	#43	Document stores
	#127	Relational DBMS

Website

cloud.google.com/bigquery

www.graphengine.io

www.actian.com/databases/ingres

www.sap.com/products/hana.html

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

cloud.google.com/bigquery/docs

www.graphengine.io/docs/manual

docs.actian.com/ingres

help.sap.com/hana

ydb.tech/en/docs

Developer

Google

Microsoft

Actian Corporation

SAP

Yandex

Initial release

2010

1974

originally developed at University Berkely in early 1970s

2010

2019

Current release

11.2, May 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

MIT License

commercial

Open Source

Apache 2.0; commercial license available

Cloud-based only

Only available as a cloud service

yes

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

hosted

.NET

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Appliance or cloud-service

Linux

Data scheme

yes

Flexible Schema (defined schema, partial schema, 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.

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

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (YQL)

APIs and other access methods

RESTful HTTP/JSON API

RESTful HTTP API

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

JDBC
ODBC

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
F#
Visual Basic

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Ingres Star to access multiple databases simultaneously

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Ingres Replicator

yes

Active-passive shard replication

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

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

Durability

Support for making data persistent

yes

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

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

yes

Access rights defined for Yandex Cloud users

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.