DBMS > Atos Standard Common Repository vs. Microsoft Access vs. Snowflake vs. Transbase

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

Please select another system to include it in the comparison.

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

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

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store
Key-value store

Relational DBMS

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

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

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

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

www.snowflake.com

www.transaction.de/en/products/transbase.html

Technical documentation

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

www.transaction.de/en/products/transbase/features.html

Developer

Atos Convergence Creators

Microsoft

Snowflake Computing Inc.

Transaction Software GmbH

Initial release

2016

1992

2014

1987

Current release

1703

1902 (16.0.11328.20222), March 2019

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

free development license

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

C and C++

Server operating systems

Linux

Windows

Not a real database server, but making use of DLLs

hosted

FreeBSD
Linux
macOS
Solaris
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

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

APIs and other access methods

LDAP

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages with LDAP bindings

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

JavaScript (Node.js)
Python

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

user defined functions

yes

Triggers

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

Source-replica replication

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

yes

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

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

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

fine grained access rights according to SQL-standard

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.