DBMS > HEAVY.AI vs. Microsoft Access vs. Oracle vs. Prometheus

System Properties Comparison HEAVY.AI vs. Microsoft Access vs. Oracle vs. Prometheus

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Widely used RDBMS

Open-source Time Series DBMS and monitoring system

Primary database model

Relational DBMS

Time Series 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	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Website

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

www.microsoft.com/en-us/microsoft-365/access

www.oracle.com/database

prometheus.io

Technical documentation

docs.heavy.ai

developer.microsoft.com/en-us/access

docs.oracle.com/en/database

prometheus.io/docs

Developer

HEAVY.AI, Inc.

Microsoft

Oracle

Initial release

2016

1992

1980

2015

Current release

5.10, January 2022

1902 (16.0.11328.20222), March 2019

23c, September 2023

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

commercial

Bundled with Microsoft Office

commercial

restricted free version is available

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++ and CUDA

C++

C and C++

Server operating systems

Linux

Windows

Not a real database server, but making use of DLLs

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

Linux
Windows

Data scheme

yes

Schemaless in JSON and XML columns

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
Thrift
Vega

ADO.NET
DAO
ODBC
OLE DB

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

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

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

PL/SQL

also stored procedures in Java possible

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

none

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Multi-source replication
Source-replica replication

yes

by Federation

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

none

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

but no files for transaction logging

ACID

isolation level can be parameterized

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

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

fine grained access rights according to SQL-standard

a simple user-level security was built in till version Access 2003

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.