DBMS > 4D vs. Microsoft Azure Data Explorer vs. Microsoft SQL Server vs. SAP SQL Anywhere vs. VoltDB

System Properties Comparison 4D vs. Microsoft Azure Data Explorer vs. Microsoft SQL Server vs. SAP SQL Anywhere vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

Fully managed big data interactive analytics platform

Microsofts flagship relational DBMS

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

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

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

Score	2.47
Rank	#110	Overall
	#54	Relational DBMS

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

www.4d.com

azure.microsoft.com/services/data-explorer

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

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

www.voltdb.com

Technical documentation

developer.4d.com

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

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

help.sap.com/docs/SAP_SQL_Anywhere

docs.voltdb.com

Developer

4D, Inc

Microsoft

SAP

formerly Sybase

VoltDB Inc.

Initial release

1984

2019

1989

1992

2010

Current release

v20, April 2023

cloud service with continuous releases

SQL Server 2022, November 2022

17, July 2015

11.3, April 2022

License

Commercial or Open Source

commercial

restricted free version is available

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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++

Java, C++

Server operating systems

OS X
Windows

hosted

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux
OS X

for development

Data scheme

yes

Fixed schema with schema-less datatypes (dynamic)

yes

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

yes

close to SQL 92

Kusto Query Language (KQL), SQL subset

yes

only a subset of SQL 99

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

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

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

ADO.NET
HTTP API
JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

4D proprietary IDE
PHP

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

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

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

Yes, possible languages: KQL, Python, R

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

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

Java

Triggers

yes

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

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

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

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

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

yes, but depending on the SQL-Server Edition

Source-replica replication

Database mirroring

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

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

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

yes

User concepts

Access control

Users and groups

Azure Active Directory Authentication

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

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.