DBMS > IBM Cloudant vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Data Explorer vs. SAP HANA

System Properties Comparison IBM Cloudant vs. Microsoft Access vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Data Explorer vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering based on Apache CouchDB

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.)

Globally distributed, horizontally scalable, multi-model database service

Fully managed big data interactive analytics platform

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Document store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

column oriented

Relational DBMS

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

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	2.73
Rank	#108	Overall
	#20	Document stores

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	29.85
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	5.16
Rank	#69	Overall
	#37	Relational DBMS

Score	45.84
Rank	#22	Overall
	#16	Relational DBMS

Website

www.ibm.com/products/cloudant

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

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/services/data-explorer

www.sap.com/products/hana.html

Technical documentation

cloud.ibm.com/docs/Cloudant

developer.microsoft.com/en-us/access

learn.microsoft.com/azure/cosmos-db

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

help.sap.com/hana

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

SAP

Initial release

2010

1992

2014

2019

2010

Current release

1902 (16.0.11328.20222), March 2019

cloud service with continuous releases

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Erlang

C++

Server operating systems

hosted

Windows

Not a real database server, but making use of DLLs

hosted

Appliance or cloud-service

Data scheme

schema-free

yes

schema-free

Fixed schema with schema-less datatypes (dynamic)

yes

Typing

predefined data types such as float or date

yes

JSON types

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 properties auto-indexed by default

all fields are automatically indexed

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like query language

Kusto Query Language (KQL), SQL subset

yes

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
DAO
ODBC
OLE DB

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

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

JDBC
ODBC

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

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

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

yes

since Access 2010 using the ACE-engine

JavaScript

Yes, possible languages: KQL, Python, R

SQLScript, R

Triggers

yes

since Access 2010 using the ACE-engine

JavaScript

yes

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

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

yes

Implicit feature of the cloud service

yes

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

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

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

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

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 operations within a document possible

ACID

but no files for transaction logging

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

User concepts

Access control

Access rights for users can be defined per database

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

Access rights can be defined down to the item level

Azure Active Directory Authentication

yes

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.