DBMS > EJDB vs. Microsoft Access vs. SAP Advantage Database Server vs. SiteWhere

System Properties Comparison EJDB vs. Microsoft Access vs. SAP Advantage Database Server vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

Low-cost RDBMS with access to ISAM and FoxPro data structures

M2M integration platform for persisting/querying time series data

Primary database model

Document store

Relational DBMS

Time Series DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

github.com/Softmotions/ejdb

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

www.sap.com/products/advantage-database-server.html

github.com/sitewhere/sitewhere

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

developer.microsoft.com/en-us/access

sitewhere1.sitewhere.io/index.html

Developer

Softmotions

Microsoft

Sybase, SAP

SiteWhere

Initial release

2012

1992

1993

2010

Current release

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

GPLv2

commercial

Bundled with Microsoft Office

commercial

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

Java

Server operating systems

server-less

Windows

Not a real database server, but making use of DLLs

Linux
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

predefined scheme

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

APIs and other access methods

in-process shared library

ADO.NET
DAO
ODBC
OLE DB

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

HTTP REST

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

Delphi
Perl
PHP

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

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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.

caching of (temporary) tables can be configured

User concepts

Access control

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

fine grained access rights according to SQL-standard

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MS Access drops in DB-Engines Ranking
2 May 2013, Paul Andlinger

Microsoft SQL Server regained rank 2 in the DB-Engines popularity ranking
3 December 2012, Matthias Gelbmann

New DB-Engines Ranking shows the popularity of database management systems
3 October 2012, Matthias Gelbmann, Paul Andlinger

show all

Recent citations in the news

Abusing Microsoft Access "Linked Table" Feature to Perform NTLM Forced Authentication Attacks
9 November 2023, Check Point Research

Hackers Exploit Microsoft Access Feature to Steal Windows User’s NTLM Tokens
11 November 2023, CybersecurityNews

MS access program to increase awareness and independence of those living with MS and disability
10 July 2023, Nebraska Medicine

After installing Navisworks, Office 2016 (32-bit) applications stopped launching
8 October 2023, Autodesk Redshift

ACCDE File (What It Is and How to Open One)
27 July 2023, Lifewire

provided by Google News

SAP Announces Q3 2023 Results: Asia Pacific and Japan View
19 October 2023, SAP News

provided by Google News

11 Best Open source IoT Platforms To Develop Smart Projects
9 March 2023, H2S Media

provided by Google News

Share this page