DBMS > Microsoft Access vs. Oracle Rdb vs. RavenDB vs. SQLite

System Properties Comparison Microsoft Access vs. Oracle Rdb vs. RavenDB vs. SQLite

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Document store

Relational DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	93.76
Rank	#12	Overall
	#8	Relational DBMS

Score	1.04
Rank	#184	Overall
	#84	Relational DBMS

Score	2.68
Rank	#102	Overall
	#19	Document stores

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

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

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

ravendb.net

www.sqlite.org

Technical documentation

developer.microsoft.com/en-us/access

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

ravendb.net/docs

www.sqlite.org/docs.html

Developer

Microsoft

Oracle, originally developed by Digital Equipment Corporation (DEC)

Hibernating Rhinos

Dwayne Richard Hipp

Initial release

1992

1984

2010

2000

Current release

1902 (16.0.11328.20222), March 2019

7.4.1.1, 2021

5.4, July 2022

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

Open Source

AGPL version 3, commercial license available

Open Source

Public Domain

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++

Server operating systems

Windows

Not a real database server, but making use of DLLs

HP Open VMS

Linux
macOS
Raspberry Pi
Windows

server-less

Data scheme

yes

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

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

yes

SQL-like query language (RQL)

yes

SQL-92 is not fully supported

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

yes

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

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

ACID, Cluster-wide transaction available

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

User concepts

Access control

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

Authorization levels configured per client per database

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.