DBMS > Atos Standard Common Repository vs. HEAVY.AI vs. Microsoft Azure Data Explorer vs. mSQL vs. MySQL

System Properties Comparison Atos Standard Common Repository vs. HEAVY.AI vs. Microsoft Azure Data Explorer vs. mSQL vs. MySQL

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

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Fully managed big data interactive analytics platform

mSQL (Mini SQL) is a simple and lightweight RDBMS

Widely used open source RDBMS

Primary database model

Document store
Key-value store

Relational DBMS

column oriented

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Spatial DBMS

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

Document store
Spatial DBMS

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

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Score	1.27
Rank	#169	Overall
	#76	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Website

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

github.com/heavyai/heavydb
www.heavy.ai

azure.microsoft.com/services/data-explorer

hughestech.com.au/products/msql

www.mysql.com

Technical documentation

docs.heavy.ai

docs.microsoft.com/en-us/azure/data-explorer

dev.mysql.com/doc

Developer

Atos Convergence Creators

HEAVY.AI, Inc.

Microsoft

Hughes Technologies

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2016

2019

1994

1995

Current release

1703

5.10, January 2022

cloud service with continuous releases

4.4, October 2021

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

commercial

free licenses can be provided

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C++ and CUDA

C and C++

Server operating systems

Linux

hosted

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

Schema and schema-less with LDAP views

yes

Fixed schema with schema-less datatypes (dynamic)

yes

Typing

predefined data types such as float or date

optional

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-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

all fields are automatically indexed

yes

SQL

Support of SQL

yes

Kusto Query Language (KQL), SQL subset

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

with proprietary extensions

APIs and other access methods

LDAP

JDBC
ODBC
Thrift
Vega

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages with LDAP bindings

All languages supporting JDBC/ODBC/Thrift
Python

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

C
C++
Delphi
Java
Perl
PHP
Tcl

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

Yes, possible languages: KQL, Python, R

yes

proprietary syntax

Triggers

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Round robin

Sharding

Implicit feature of the cloud service

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Spark connector (open source): github.com/Azure/azure-kusto-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency
Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Atomic execution of specific operations

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Azure Active Directory Authentication

Users with fine-grained authorization concept

no user groups or roles

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.