DBMS > Atos Standard Common Repository vs. Microsoft Access vs. RocksDB vs. Sphinx vs. SWC-DB

System Properties Comparison Atos Standard Common Repository vs. Microsoft Access vs. RocksDB vs. Sphinx vs. SWC-DB

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

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)

Open source search engine for searching in data from different sources, e.g. relational databases

A high performance, scalable Wide Column DBMS

Primary database model

Document store
Key-value store

Secondary database models

Time Series DBMS

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

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

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

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	0.08
Rank	#364	Overall
	#13	Wide column stores

Website

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

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

rocksdb.org

sphinxsearch.com

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

developer.microsoft.com/en-us/access

github.com/facebook/rocksdb/wiki

sphinxsearch.com/docs

Developer

Atos Convergence Creators

Microsoft

Facebook, Inc.

Sphinx Technologies Inc.

Alex Kashirin

Initial release

2016

1992

2013

2001

2020

Current release

1703

1902 (16.0.11328.20222), March 2019

9.2.1, May 2024

3.5.1, February 2023

0.5, April 2021

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

BSD

Open Source

GPL version 2, commercial licence available

Open Source

GPL V3

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

Server operating systems

Linux

Windows

Not a real database server, but making use of DLLs

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

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

full-text index on all search fields

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like query language (SphinxQL)

SQL-like query language

APIs and other access methods

LDAP

ADO.NET
DAO
ODBC
OLE DB

C++ API
Java API

Proprietary protocol

Proprietary protocol
Thrift

Supported programming languages

All languages with LDAP bindings

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

C
C++
Go
Java
Perl
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C++

Server-side scripts

Stored procedures

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

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

none

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

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

The original contents of fields are not stored in the Sphinx index.

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

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.