DBMS > Microsoft Access vs. Oracle vs. Realm vs. SiteWhere

System Properties Comparison Microsoft Access vs. Oracle vs. Realm vs. SiteWhere

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

Widely used RDBMS

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Document store

Time Series DBMS

Secondary database models

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

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

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

www.oracle.com/database

realm.io

github.com/sitewhere/sitewhere

Technical documentation

developer.microsoft.com/en-us/access

docs.oracle.com/en/database

realm.io/docs

sitewhere1.sitewhere.io/index.html

Developer

Microsoft

Oracle

Realm, acquired by MongoDB in May 2019

SiteWhere

Initial release

1992

1980

2014

2010

Current release

1902 (16.0.11328.20222), March 2019

23c, September 2023

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

restricted free version is available

Open Source

Common Public Attribution License Version 1.0

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

C and C++

Java

Server operating systems

Windows

Not a real database server, but making use of DLLs

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

Android
Backend: server-less
iOS
Windows

Linux
OS X
Windows

Data scheme

yes

Schemaless in JSON and XML columns

yes

predefined scheme

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

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

with proprietary extensions

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP REST

Supported programming languages

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

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
Java

with Android only
Objective-C
React Native
Swift

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

PL/SQL

also stored procedures in Java possible

runs within the applications so server-side scripts are unnecessary

Triggers

yes

since Access 2010 using the ACE-engine

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

none

Sharding, horizontal partitioning

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

none

selectable replication factor

based on HBase

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

In-Memory realm

User concepts

Access control

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

fine grained access rights according to SQL-standard

yes

Users with fine-grained authorization concept

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.