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

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

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

www.kinetica.com

azure.microsoft.com/services/data-explorer

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

github.com/sitewhere/sitewhere

Technical documentation

docs.kinetica.com

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

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

sitewhere1.sitewhere.io/index.html

Developer

Kinetica

Microsoft

SiteWhere

Initial release

2012

2019

1989

2010

Current release

7.1, August 2021

cloud service with continuous releases

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

Common Public Attribution License Version 1.0

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

C, C++

C++

Java

Server operating systems

Linux

hosted

Linux
Windows

Linux
OS X
Windows

Data scheme

yes

Fixed schema with schema-less datatypes (dynamic)

yes

predefined scheme

Typing

predefined data types such as float or date

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

SQL-like DML and DDL statements

Kusto Query Language (KQL), SQL subset

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

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

HTTP REST

Supported programming languages

C++
Java
JavaScript (Node.js)
Python

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

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

Server-side scripts

Stored procedures

user defined functions

Yes, possible languages: KQL, Python, R

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

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

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

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

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

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

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

yes, but depending on the SQL-Server Edition

selectable replication factor

based on HBase

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

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of 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

GPU vRAM or System RAM

yes

User concepts

Access control

Access rights for users and roles on table level

Azure Active Directory Authentication

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.