DBMS > Atos Standard Common Repository vs. EsgynDB vs. MaxDB vs. SAP HANA

System Properties Comparison Atos Standard Common Repository vs. EsgynDB vs. MaxDB vs. SAP HANA

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

A robust and reliable RDBMS optimized to run all major SAP solutions

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Document store
Key-value store

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	2.26
Rank	#114	Overall
	#55	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

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

www.esgyn.cn

maxdb.sap.com

www.sap.com/products/hana.html

Technical documentation

maxdb.sap.com/documentation

help.sap.com/hana

Developer

Atos Convergence Creators

Esgyn

SAP, acquired from Software AG (Adabas-D) in 1997

SAP

Initial release

2016

2015

1984

2010

Current release

1703

7.9.10.12, February 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Limited community edition free

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++, Java

C++

Server operating systems

Linux

AIX
HP-UX
Linux
Solaris
Windows

Appliance or cloud-service

Data scheme

Schema and schema-less with LDAP views

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

APIs and other access methods

LDAP

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
WebDAV

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

All languages supporting JDBC/ODBC/ADO.Net

.Net
C#
Java
Perl
PHP
Python

Server-side scripts

Stored procedures

Java Stored Procedures

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication between multi datacenters

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

yes

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.