DBMS > Microsoft Access vs. Oracle Rdb vs. PouchDB vs. RocksDB vs. Sphinx

System Properties Comparison Microsoft Access vs. Oracle Rdb vs. PouchDB vs. RocksDB vs. Sphinx

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

JavaScript DBMS with an API inspired by CouchDB

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

Score	1.08
Rank	#184	Overall
	#85	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

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

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

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

www.oracle.com/database/technologies/related/rdb.html

pouchdb.com

rocksdb.org

sphinxsearch.com

Technical documentation

developer.microsoft.com/en-us/access

www.oracle.com/database/technologies/related/rdb-doc.html

pouchdb.com/guides

github.com/facebook/rocksdb/wiki

sphinxsearch.com/docs

Developer

Microsoft

Oracle, originally developed by Digital Equipment Corporation (DEC)

Apache Software Foundation

Facebook, Inc.

Sphinx Technologies Inc.

Initial release

1992

1984

2012

2013

2001

Current release

1902 (16.0.11328.20222), March 2019

7.4.1.1, 2021

7.1.1, June 2019

8.11.4, April 2024

3.5.1, February 2023

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

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

C++

JavaScript

C++

Server operating systems

Windows

Not a real database server, but making use of DLLs

HP Open VMS

server-less, requires a JavaScript environment (browser, Node.js)

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

Flexible Schema (defined schema, partial schema, schema free)

schema-free

yes

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.

Secondary indexes

yes

via views

yes

full-text index on all search fields

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

SQL-like query language (SphinxQL)

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

HTTP REST

only for PouchDB Server
JavaScript API

C++ API
Java API

Proprietary protocol

Supported programming languages

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

JavaScript

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

yes

since Access 2010 using the ACE-engine

View functions in JavaScript

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal partitioning

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual 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

yes, on a single node

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

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.