DBMS > Atos Standard Common Repository vs. DuckDB vs. Linter vs. Microsoft Access vs. RocksDB

System Properties Comparison Atos Standard Common Repository vs. DuckDB vs. Linter vs. Microsoft Access vs. RocksDB

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

An embeddable, in-process, column-oriented SQL OLAP RDBMS

RDBMS for high security requirements

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store

Secondary database models

Spatial DBMS

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

Score	4.63
Rank	#69	Overall
	#37	Relational DBMS

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

duckdb.org

linter.ru

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

rocksdb.org

Technical documentation

duckdb.org/docs

developer.microsoft.com/en-us/access

github.com/facebook/rocksdb/wiki

Developer

Atos Convergence Creators

relex.ru

Microsoft

Facebook, Inc.

Initial release

2016

2018

1990

1992

2013

Current release

1703

1.0.0, June 2024

1902 (16.0.11328.20222), March 2019

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

MIT License

commercial

Bundled with Microsoft Office

Open Source

BSD

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

Java

C++

C and C++

C++

Server operating systems

Linux

server-less

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Windows

Not a real database server, but making use of DLLs

Linux

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

Typing

predefined data types such as float or date

optional

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

APIs and other access methods

LDAP

Arrow Database Connectivity (ADBC)
CLI Client
JDBC
ODBC

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

ADO.NET
DAO
ODBC
OLE DB

C++ API
Java API

Supported programming languages

All languages with LDAP bindings

C
C#

3rd party driver
C++
Crystal

3rd party driver
Go

3rd party driver
Java
Lisp

3rd party driver
Python
R
Ruby

3rd party driver
Rust
Swift
Zig

3rd party driver

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

yes

since Access 2010 using the ACE-engine

Triggers

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

but no files for transaction logging

yes

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

User concepts

Access control

LDAP bind authentication

fine grained access rights according to SQL-standard

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.