DBMS > Atos Standard Common Repository vs. Snowflake vs. Teradata Aster vs. Tibero

System Properties Comparison Atos Standard Common Repository vs. Snowflake vs. Teradata Aster vs. Tibero

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.

Teradata Aster has been integrated into other Teradata systems and therefore 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

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

Platform for big data analytics on multistructured data sources and types

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Document store
Key-value store

Relational DBMS

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

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	1.81
Rank	#143	Overall
	#65	Relational DBMS

Website

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

www.snowflake.com

us.tmaxsoft.com/products/tibero

Technical documentation

docs.snowflake.net/manuals/index.html

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Atos Convergence Creators

Snowflake Computing Inc.

Teradata

TmaxSoft

Initial release

2016

2014

2005

2003

Current release

1703

6, April 2015

License

Commercial or Open Source

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 and Assembler

Server operating systems

Linux

hosted

Linux

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

Schema and schema-less with LDAP views

yes

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

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

in Aster File Store

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

LDAP

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC
OLE DB

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

All languages with LDAP bindings

JavaScript (Node.js)
Python

C
C#
C++
Java
Python
R

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

user defined functions

R packages

Persistent Stored Procedure (PSM)

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

yes

Sharding

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

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

planned for next version

User concepts

Access control

LDAP bind authentication

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

fine grained access rights according to SQL-standard

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.