DBMS > Adabas vs. Databend vs. GeoSpock vs. Microsoft SQL Server

System Properties Comparison Adabas vs. Databend vs. GeoSpock vs. Microsoft SQL Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

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

used typically together with the Natural programming platform

An open-source, elastic, and workload-aware cloud data warehouse designed to meet businesses' massive-scale analytics needs at low cost and with low complexity

Spatial and temporal data processing engine for extreme data scale

Microsofts flagship relational DBMS

Primary database model

Multivalue DBMS

Relational DBMS

Secondary database models

Time Series DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	2.64
Rank	#104	Overall
	#1	Multivalue DBMS

Score	0.28
Rank	#287	Overall
	#131	Relational DBMS

Score	807.76
Rank	#3	Overall
	#3	Relational DBMS

Website

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

github.com/datafuselabs/databend
www.databend.com

geospock.com

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

Technical documentation

docs.databend.com

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

Developer

Software AG

Databend Labs

GeoSpock

Microsoft

Initial release

1971

2021

1989

Current release

1.0.59, April 2023

2.0, September 2019

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

restricted free version is available

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

Rust

Java, Javascript

C++

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

hosted
Linux
macOS

hosted

Linux
Windows

Data scheme

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

temporal, categorical

yes

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

yes

ANSI SQL for query only (using Presto)

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

CLI Client
JDBC
RESTful HTTP API

JDBC

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

Supported programming languages

Natural

Go
Java
JavaScript (Node.js)
Python
Rust

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

Server-side scripts

Stored procedures

in Natural

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

none

Automatic sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

none

yes, but depending on the SQL-Server Edition

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

yes

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)

Users with fine-grained authorization concept, user roles

Access rights for users can be defined per table

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.