DBMS > Microsoft Access vs. Microsoft Azure SQL Database vs. Oracle vs. Oracle Berkeley DB vs. Yaacomo

System Properties Comparison Microsoft Access vs. Microsoft Azure SQL Database vs. Oracle vs. Oracle Berkeley DB vs. Yaacomo

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

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

Database as a Service offering with high compatibility to Microsoft SQL Server

Widely used RDBMS

Widely used in-process key-value store

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	78.40
Rank	#15	Overall
	#10	Relational DBMS

Score	1234.27
Rank	#1	Overall
	#1	Relational DBMS

Score	2.52
Rank	#114	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Website

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

azure.microsoft.com/en-us/products/azure-sql/database

www.oracle.com/database

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

yaacomo.com

Technical documentation

developer.microsoft.com/en-us/access

docs.microsoft.com/en-us/azure/azure-sql

docs.oracle.com/en/database

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Q2WEB GmbH

Initial release

1992

2010

1980

1994

2009

Current release

1902 (16.0.11328.20222), March 2019

V12

23c, September 2023

18.1.40, May 2020

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

restricted free version is available

Open Source

commercial license available

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

C and C++

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

Windows

Not a real database server, but making use of DLLs

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Android
Linux
Windows

Data scheme

yes

Schemaless in JSON and XML columns

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.

yes

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

with proprietary extensions

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

JDBC
ODBC

Supported programming languages

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

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

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

Transact SQL

PL/SQL

also stored procedures in Java possible

Triggers

yes

since Access 2010 using the ACE-engine

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding, horizontal partitioning

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, with always 3 replicas available

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

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

ACID

isolation level can be parameterized

ACID

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

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

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

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.