DBMS > Atos Standard Common Repository vs. BaseX vs. Google BigQuery vs. Teradata

System Properties Comparison Atos Standard Common Repository vs. BaseX vs. Google BigQuery vs. Teradata

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

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

Large scale data warehouse service with append-only tables

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Document store
Key-value store

Native XML DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	1.84
Rank	#135	Overall
	#4	Native XML DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Website

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

basex.org

cloud.google.com/bigquery

www.teradata.com

Technical documentation

docs.basex.org

cloud.google.com/bigquery/docs

docs.teradata.com

Developer

Atos Convergence Creators

BaseX GmbH

Google

Teradata

Initial release

2016

2007

2010

1984

Current release

1703

10.7, August 2023

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

commercial

Open Source

BSD license

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

Server operating systems

Linux

Linux
OS X
Windows

hosted

hosted
Linux

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

optional

XQuery supports types

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

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes

SQL 2016 + extensions

APIs and other access methods

LDAP

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

RESTful HTTP/JSON API

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

All languages with LDAP bindings

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

via events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication
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

multiple readers, single writer

Since BigQuery is designed for querying data

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

Users with fine-grained authorization concept on 4 levels

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.