DBMS > Atos Standard Common Repository vs. Microsoft Access vs. Microsoft Azure Data Explorer vs. Oracle vs. Sadas Engine

System Properties Comparison Atos Standard Common Repository vs. Microsoft Access vs. Microsoft Azure Data Explorer vs. Oracle vs. Sadas Engine

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

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Fully managed big data interactive analytics platform

Widely used RDBMS

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

Document store
Key-value store

Relational DBMS

column oriented

Relational DBMS

Secondary database models

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
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Website

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

www.microsoft.com/en-us/microsoft-365/access

azure.microsoft.com/services/data-explorer

www.oracle.com/database

www.sadasengine.com

Technical documentation

developer.microsoft.com/en-us/access

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

docs.oracle.com/en/database

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Atos Convergence Creators

Microsoft

Oracle

SADAS s.r.l.

Initial release

2016

1992

2019

1980

2006

Current release

1703

1902 (16.0.11328.20222), March 2019

cloud service with continuous releases

23c, September 2023

8.0

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

restricted free version is available

commercial

free trial version 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.

Implementation language

Java

C++

C and C++

C++

Server operating systems

Linux

Windows

Not a real database server, but making use of DLLs

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

AIX
Linux
Windows

Data scheme

Schema and schema-less with LDAP views

yes

Fixed schema with schema-less datatypes (dynamic)

yes

Schemaless in JSON and XML columns

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

but not compliant to any SQL standard

Kusto Query Language (KQL), SQL subset

yes

with proprietary extensions

yes

APIs and other access methods

LDAP

ADO.NET
DAO
ODBC
OLE DB

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

JDBC
ODBC
Proprietary protocol

Supported programming languages

All languages with LDAP bindings

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

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

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

Yes, possible languages: KQL, Python, R

PL/SQL

also stored procedures in Java possible

Triggers

yes

since Access 2010 using the ACE-engine

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

none

Sharding

Implicit feature of the cloud service

Sharding, horizontal partitioning

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

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

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

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

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency

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

but no files for transaction logging

ACID

isolation level can be parameterized

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

managed by 'Learn by Usage'

User concepts

Access control

LDAP bind authentication

a simple user-level security was built in till version Access 2003

Azure Active Directory Authentication

fine grained access rights according to SQL-standard

Access rights for users, groups and roles 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.