DBMS > Adabas vs. Apache Drill vs. Google BigQuery vs. IBM Db2 warehouse vs. Kinetica

System Properties Comparison Adabas vs. Apache Drill vs. Google BigQuery vs. IBM Db2 warehouse vs. Kinetica

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

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Large scale data warehouse service with append-only tables

Cloud-based data warehousing service

Fully vectorized database across both GPUs and CPUs

Primary database model

Multivalue DBMS

Document store
Relational DBMS

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	3.17
Rank	#94	Overall
	#1	Multivalue DBMS

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	1.30
Rank	#164	Overall
	#75	Relational DBMS

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Website

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

drill.apache.org

cloud.google.com/bigquery

www.ibm.com/products/db2/warehouse

www.kinetica.com

Technical documentation

drill.apache.org/docs

cloud.google.com/bigquery/docs

docs.kinetica.com

Developer

Software AG

Apache Software Foundation

Google

IBM

Kinetica

Initial release

1971

2012

2010

2014

2012

Current release

1.20.3, January 2023

7.1, August 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

commercial

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

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

Linux
OS X
Windows

hosted

Linux

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.

Import/export of XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

SQL SELECT statement is SQL:2003 compliant

yes

SQL-like DML and DDL statements

APIs and other access methods

HTTP API

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

with add-on software Adabas SOA Gateway

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

.NET Client API
JDBC
ODBC
OLE DB

JDBC
ODBC
RESTful HTTP API

Supported programming languages

Natural

C++

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

in Natural

user defined functions

in JavaScript

PL/SQL, SQL PL

user defined functions

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

yes

GPU vRAM or System RAM

User concepts

Access control

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

Depending on the underlying data source

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

Access rights for users and roles on table level

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.