DBMS > HBase vs. Microsoft Access vs. Quasardb vs. SAP HANA

System Properties Comparison HBase vs. Microsoft Access vs. Quasardb vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Wide-column store based on Apache Hadoop and on concepts of BigTable

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

Distributed, high-performance timeseries database

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

Primary database model

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	31.25
Rank	#26	Overall
	#2	Wide column stores

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	0.19
Rank	#327	Overall
	#30	Time Series DBMS

Score	45.84
Rank	#22	Overall
	#16	Relational DBMS

Website

hbase.apache.org

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

quasar.ai

www.sap.com/products/hana.html

Technical documentation

hbase.apache.org/book.html

developer.microsoft.com/en-us/access

doc.quasar.ai/master

help.sap.com/hana

Developer

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Microsoft

quasardb

SAP

Initial release

2008

1992

2009

2010

Current release

2.3.4, January 2021

1902 (16.0.11328.20222), March 2019

3.14.1, January 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Bundled with Microsoft Office

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

Java

C++

Server operating systems

Linux
Unix
Windows

using Cygwin

Windows

Not a real database server, but making use of DLLs

BSD
Linux
OS X
Windows

Appliance or cloud-service

Data scheme

schema-free, schema definition possible

yes

schema-free

yes

Typing

predefined data types such as float or date

options to bring your own types, AVRO

yes

integer and binary

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

with tags

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like query language

yes

APIs and other access methods

Java API
RESTful HTTP API
Thrift

ADO.NET
DAO
ODBC
OLE DB

HTTP API

JDBC
ODBC

Supported programming languages

C
C#
C++
Groovy
Java
PHP
Python
Scala

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

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Server-side scripts

Stored procedures

yes

Coprocessors in Java

yes

since Access 2010 using the ACE-engine

SQLScript, R

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

consistent hashing

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Source-replica replication with selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Single row ACID (across millions of columns)

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

by using LevelDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

yes

User concepts

Access control

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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

Cryptographically strong user authentication and audit trail

yes

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.