DBMS > Atos Standard Common Repository vs. Hypertable vs. MaxDB vs. Microsoft Azure AI Search vs. Snowflake

System Properties Comparison Atos Standard Common Repository vs. Hypertable vs. MaxDB vs. Microsoft Azure AI Search vs. Snowflake

Editorial information provided by DB-Engines

Name

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

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

Description

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

An open source BigTable implementation based on distributed file systems such as Hadoop

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

Search-as-a-service for web and mobile app development

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

Primary database model

Document store
Key-value store

Secondary database models

Vector DBMS

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

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Score	5.59
Rank	#63	Overall
	#7	Search engines

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

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

maxdb.sap.com

azure.microsoft.com/en-us/services/search

www.snowflake.com

Technical documentation

maxdb.sap.com/documentation

learn.microsoft.com/en-us/azure/search

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

Hypertable Inc.

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

Microsoft

Snowflake Computing Inc.

Initial release

2016

2009

1984

2015

2014

Current release

1703

0.9.8.11, March 2016

7.9.10.12, February 2024

License

Commercial or Open Source

commercial

Open Source

GNU version 3. Commercial license available

commercial

Limited community edition free

commercial

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

Linux
OS X
Windows

an inofficial Windows port is available

AIX
HP-UX
Linux
Solaris
Windows

hosted

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

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

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

restricted

only exact value or prefix value scans

yes

SQL

Support of SQL

yes

APIs and other access methods

LDAP

C++ API
Thrift

ADO.NET
JDBC
ODBC
WebDAV

RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

C++
Java
Perl
PHP
Python
Ruby

.Net
C#
Java
Perl
PHP
Python

C#
Java
JavaScript
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

Sharding

Implicit feature of the cloud service

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor on file system level

Source-replica replication

yes

Implicit feature of the cloud service

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

using Azure authentication

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.