DBMS > Adabas vs. Microsoft SQL Server vs. Realm vs. TerarkDB vs. VoltDB

System Properties Comparison Adabas vs. Microsoft SQL Server vs. Realm vs. TerarkDB vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

OLTP - DBMS for mainframes and Linux/Unix/Windows environments

used typically together with the Natural programming platform

Microsofts flagship relational DBMS

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

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

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

www.softwareag.com/en_corporate/platform/adabas-natural.html

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

realm.io

github.com/bytedance/terarkdb

www.voltdb.com

Technical documentation

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

realm.io/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

docs.voltdb.com

Developer

Software AG

Microsoft

Realm, acquired by MongoDB in May 2019

ByteDance, originally Terark

VoltDB Inc.

Initial release

1971

1989

2014

2016

2010

Current release

SQL Server 2022, November 2022

11.3, April 2022

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

commercial

restricted open source version available

Open Source

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

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Java, C++

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux
Windows

Android
Backend: server-less
iOS
Windows

Linux
OS X

for development

Data scheme

yes

schema-free

yes

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

with add-on product Adabas SQL Gateway

yes

only a subset of SQL 99

APIs and other access methods

HTTP API

with add-on software Adabas SOA Gateway
SOAP-based API

with add-on software Adabas SOA Gateway

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

C++ API
Java API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

Natural

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

.Net
Java

with Android only
Objective-C
React Native
Swift

C++
Java

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

in Natural

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

runs within the applications so server-side scripts are unnecessary

Java

Triggers

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

yes, with additonal products like Adabas Cluster Services, Adabas Parallel Services, Adabas Vista

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

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

yes, but depending on the SQL-Server Edition

none

Multi-source replication
Source-replica replication

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

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

In-Memory realm

yes

User concepts

Access control

only with OS-specific tools (e.g. IBM RACF, CA Top Secret)

fine grained access rights according to SQL-standard

yes

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.