DBMS > 4D vs. Microsoft Azure SQL Database vs. SAP HANA vs. YottaDB

System Properties Comparison 4D vs. Microsoft Azure SQL Database vs. SAP HANA vs. YottaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

Database as a Service offering with high compatibility to Microsoft SQL Server

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

A fast and solid embedded Key-value store

Primary database model

Relational DBMS

Key-value store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Relational DBMS

using the Octo plugin

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.20
Rank	#317	Overall
	#47	Key-value stores

Website

www.4d.com

azure.microsoft.com/en-us/products/azure-sql/database

www.sap.com/products/hana.html

yottadb.com

Technical documentation

developer.4d.com

docs.microsoft.com/en-us/azure/azure-sql

help.sap.com/hana

yottadb.com/resources/documentation

Developer

4D, Inc

Microsoft

SAP

YottaDB, LLC

Initial release

1984

2010

2001

Current release

v20, April 2023

V12

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

AGPL 3.0

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

C++

Server operating systems

OS X
Windows

hosted

Appliance or cloud-service

Docker
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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

SQL

Support of SQL

yes

close to SQL 92

yes

by using the Octo plugin

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

ADO.NET
JDBC
ODBC

JDBC
ODBC

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

4D proprietary IDE
PHP

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

yes

Transact SQL

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes, with always 3 replicas available

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

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

User concepts

Access control

Users and groups

fine grained access rights according to SQL-standard

yes

Users and groups based on OS-security mechanisms

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.