DBMS > Apache Drill vs. JaguarDB vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Data Explorer vs. SAP SQL Anywhere

System Properties Comparison Apache Drill vs. JaguarDB vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Data Explorer vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Performant, highly scalable DBMS for AI and IoT applications

Globally distributed, horizontally scalable, multi-model database service

Fully managed big data interactive analytics platform

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Document store
Relational DBMS

Key-value store
Vector 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

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

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

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

drill.apache.org

www.jaguardb.com

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/services/data-explorer

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

drill.apache.org/docs

www.jaguardb.com/support.html

learn.microsoft.com/azure/cosmos-db

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

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Apache Software Foundation

DataJaguar, Inc.

Microsoft

SAP

formerly Sybase

Initial release

2012

2015

2014

2019

1992

Current release

1.20.3, January 2023

3.3 July 2023

cloud service with continuous releases

17, July 2015

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GPL V3.0

commercial

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

C++

the server part. Clients available in other languages

Server operating systems

Linux
OS X
Windows

Linux

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows

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

SQL SELECT statement is SQL:2003 compliant

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like query language

Kusto Query Language (KQL), SQL subset

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

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

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

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

C++

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

.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

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

JavaScript

Yes, possible languages: KQL, Python, R

yes, in C/C++, Java, .Net or Perl

Triggers

JavaScript

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

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Implicit feature of the cloud service

yes

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

Source-replica replication

Database mirroring

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

none

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

rights management via user accounts

Access rights can be defined down to the item level

Azure Active Directory Authentication

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.