DBMS > Atos Standard Common Repository vs. EXASOL vs. Google BigQuery vs. Microsoft SQL Server vs. XTDB

System Properties Comparison Atos Standard Common Repository vs. EXASOL vs. Google BigQuery vs. Microsoft SQL Server vs. XTDB

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Large scale data warehouse service with append-only tables

Microsofts flagship relational DBMS

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Document store
Key-value store

Relational DBMS

Document store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	2.25
Rank	#120	Overall
	#57	Relational DBMS

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	0.09
Rank	#351	Overall
	#47	Document stores

Website

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

www.exasol.com

cloud.google.com/bigquery

www.microsoft.com/en-us/sql-server

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

www.exasol.com/resources

cloud.google.com/bigquery/docs

learn.microsoft.com/en-US/sql/sql-server

www.xtdb.com/docs

Developer

Atos Convergence Creators

Exasol

Google

Microsoft

Juxt Ltd.

Initial release

2016

2000

2010

1989

2019

Current release

1703

SQL Server 2022, November 2022

1.19, September 2021

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

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

Clojure

Server operating systems

Linux

hosted

Linux
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

Typing

predefined data types such as float or date

optional

yes

yes, extensible-data-notation format

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

limited SQL, making use of Apache Calcite

APIs and other access methods

LDAP

.Net
JDBC
ODBC
WebSocket

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

HTTP REST
JDBC

Supported programming languages

All languages with LDAP bindings

Java
Lua
Python
R

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

tables can be distributed across several files (horizontal partitioning); sharding through federation

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, but depending on the SQL-Server Edition

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

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

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

Access rights for users, groups and roles according to SQL-standard

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.