DBMS > Microsoft Access vs. Oracle NoSQL vs. SAP HANA vs. Transbase

System Properties Comparison Microsoft Access vs. Oracle NoSQL vs. SAP HANA vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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.)

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

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

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Relational DBMS

Document store
Key-value store
Relational DBMS

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	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	2.96
Rank	#103	Overall
	#18	Document stores
	#17	Key-value stores
	#52	Relational DBMS

Score	45.84
Rank	#22	Overall
	#16	Relational DBMS

Score	0.15
Rank	#337	Overall
	#147	Relational DBMS

Website

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

www.oracle.com/database/nosql/technologies/nosql

www.sap.com/products/hana.html

www.transaction.de/en/products/transbase.html

Technical documentation

developer.microsoft.com/en-us/access

docs.oracle.com/en/database/other-databases/nosql-database/index.html

help.sap.com/hana

www.transaction.de/en/products/transbase/features.html

Developer

Microsoft

Oracle

SAP

Transaction Software GmbH

Initial release

1992

2011

2010

1987

Current release

1902 (16.0.11328.20222), March 2019

23.3, December 2023

2.0 SPS07 (April 4, 2023), April 2023

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

commercial

free development license

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

C and C++

Server operating systems

Windows

Not a real database server, but making use of DLLs

Linux
Solaris SPARC/x86

Appliance or cloud-service

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

Typing

predefined data types such as float or date

yes

optional

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.

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like DML and DDL statements

yes

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

RESTful HTTP API

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

C
C#
Go
Java
JavaScript (Node.js)
Python

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

SQLScript, R

yes

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

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

configurable

ACID within a storage node (=shard)

ACID

yes

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

off heap cache

yes

User concepts

Access control

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

Access rights for users and roles

yes

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.