DBMS > EXASOL vs. HBase vs. Microsoft Access vs. RocksDB vs. Sphinx

System Properties Comparison EXASOL vs. HBase vs. Microsoft Access vs. RocksDB vs. Sphinx

Editorial information provided by DB-Engines

Name

Description

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

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

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

www.exasol.com

hbase.apache.org

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

rocksdb.org

sphinxsearch.com

Technical documentation

www.exasol.com/resources

hbase.apache.org/book.html

developer.microsoft.com/en-us/access

github.com/facebook/rocksdb/wiki

sphinxsearch.com/docs

Developer

Exasol

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Microsoft

Facebook, Inc.

Sphinx Technologies Inc.

Initial release

2000

2008

1992

2013

2001

Current release

2.3.4, January 2021

1902 (16.0.11328.20222), March 2019

8.11.4, April 2024

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache version 2

commercial

Bundled with Microsoft Office

Open Source

BSD

Open Source

GPL version 2, commercial licence available

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

Java

C++

Server operating systems

Linux
Unix
Windows

using Cygwin

Windows

Not a real database server, but making use of DLLs

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

schema-free, schema definition possible

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

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

full-text index on all search fields

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like query language (SphinxQL)

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

Java API
RESTful HTTP API
Thrift

ADO.NET
DAO
ODBC
OLE DB

C++ API
Java API

Proprietary protocol

Supported programming languages

Java
Lua
Python
R

C
C#
C++
Groovy
Java
PHP
Python
Scala

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

C
C++
Go
Java
Perl
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

user defined functions

yes

Coprocessors in Java

yes

since Access 2010 using the ACE-engine

Triggers

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Single row ACID (across millions of columns)

ACID

but no files for transaction logging

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

The original contents of fields are not stored in the Sphinx index.

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 rights for users, groups and roles according to SQL-standard

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

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.