DBMS > Google BigQuery vs. HEAVY.AI vs. Ingres vs. Oracle

System Properties Comparison Google BigQuery vs. HEAVY.AI vs. Ingres vs. Oracle

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Well established RDBMS

Widely used RDBMS

Primary database model

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Website

cloud.google.com/bigquery

github.com/heavyai/heavydb
www.heavy.ai

www.actian.com/databases/ingres

www.oracle.com/database

Technical documentation

cloud.google.com/bigquery/docs

docs.heavy.ai

docs.actian.com/ingres

docs.oracle.com/en/database

Developer

Google

HEAVY.AI, Inc.

Actian Corporation

Oracle

Initial release

2010

2016

1974

originally developed at University Berkely in early 1970s

1980

Current release

5.10, January 2022

11.2, May 2022

23c, September 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

commercial

restricted free version is available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++ and CUDA

C and C++

Server operating systems

hosted

Linux

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Data scheme

yes

Schemaless in JSON and XML columns

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

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC
Thrift
Vega

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

All languages supporting JDBC/ODBC/Thrift
Python

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

PL/SQL

also stored procedures in Java possible

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Round robin

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Ingres Replicator

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

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

isolation level can be parameterized

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

Version 12c introduced the new option 'Oracle Database In-Memory'

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

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.