DBMS > Adabas vs. Google Cloud Datastore vs. Microsoft SQL Server vs. Riak KV

System Properties Comparison Adabas vs. Google Cloud Datastore vs. Microsoft SQL Server vs. Riak KV

Please select another system to include it in the comparison.

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Microsofts flagship relational DBMS

Distributed, fault tolerant key-value store

Primary database model

with links between data sets and object tags for the creation of secondary indexes

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	3.58
Rank	#91	Overall
	#1	Multivalue DBMS

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Website

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

cloud.google.com/datastore

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

Technical documentation

cloud.google.com/datastore/docs

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

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Software AG

Google

Microsoft

OpenSource, formerly Basho Technologies

Initial release

1971

2008

1989

2009

Current release

SQL Server 2022, November 2022

3.2.0, December 2022

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

hosted

Linux
Windows

Linux
OS X

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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

restricted

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

SQL-like query language (GQL)

yes

APIs and other access methods

HTTP API

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

with add-on software Adabas SOA Gateway

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

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

HTTP API
Native Erlang Interface

Supported programming languages

Natural

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

in Natural

using Google App Engine

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

Erlang

Triggers

Callbacks using the Google Apps Engine

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

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

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

Multi-source replication using Paxos

yes, but depending on the SQL-Server Edition

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

links between data sets can be stored

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

User concepts

Access control

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

yes, using Riak Security

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.