DBMS > Atos Standard Common Repository vs. Citus vs. Microsoft Access vs. Snowflake vs. STSdb

System Properties Comparison Atos Standard Common Repository vs. Citus vs. Microsoft Access vs. Snowflake vs. STSdb

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

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

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

Cloud-based data warehousing service for structured and semi-structured data

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store

Secondary database models

Document store

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

Score	2.21
Rank	#118	Overall
	#56	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

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

www.citusdata.com

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

www.snowflake.com

github.com/STSSoft/STSdb4

Technical documentation

docs.citusdata.com

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

Microsoft

Snowflake Computing Inc.

STS Soft SC

Initial release

2016

2010

1992

2014

2011

Current release

1703

8.1, December 2018

1902 (16.0.11328.20222), March 2019

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

AGPL, commercial license also available

commercial

Bundled with Microsoft Office

commercial

Open Source

GPLv2, commercial license available

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

Java

C++

Server operating systems

Linux

Windows

Not a real database server, but making use of DLLs

hosted

Windows

Data scheme

Schema and schema-less with LDAP views

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

optional

yes

primitive types and user defined types (classes)

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

specific XML type available, but no XML query functionality

yes

Secondary indexes

yes

SQL

Support of SQL

yes

standard, with numerous extensions

yes

but not compliant to any SQL standard

yes

APIs and other access methods

LDAP

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

.NET Client API

Supported programming languages

All languages with LDAP bindings

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

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

JavaScript (Node.js)
Python

C#
Java

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

yes

since Access 2010 using the ACE-engine

user defined functions

Triggers

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

other methods possible by using 3rd party extensions

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

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

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

Users with fine-grained authorization concept, user roles and pluggable authentication

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.