DBMS > Adabas vs. Drizzle vs. JaguarDB vs. Microsoft SQL Server vs. Prometheus

System Properties Comparison Adabas vs. Drizzle vs. JaguarDB vs. Microsoft SQL Server vs. Prometheus

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

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

used typically together with the Natural programming platform

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Performant, highly scalable DBMS for AI and IoT applications

Microsofts flagship relational DBMS

Open-source Time Series DBMS and monitoring system

Primary database model

Multivalue DBMS

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Time Series DBMS

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	0.09
Rank	#356	Overall
	#53	Key-value stores
	#13	Vector DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	7.92
Rank	#51	Overall
	#2	Time Series DBMS

Website

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

www.jaguardb.com

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

prometheus.io

Technical documentation

www.jaguardb.com/support.html

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

prometheus.io/docs

Developer

Software AG

Drizzle project, originally started by Brian Aker

DataJaguar, Inc.

Microsoft

Initial release

1971

2008

2015

1989

2015

Current release

7.2.4, September 2012

3.3 July 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

GPL V3.0

commercial

restricted free version is available

Open Source

Apache 2.0

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

the server part. Clients available in other languages

C++

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

FreeBSD
Linux
OS X

Linux

Linux
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

yes

with proprietary extensions

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

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

JDBC

JDBC
ODBC

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

RESTful HTTP/JSON API

Supported programming languages

Natural

C
C++
Java
PHP

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Server-side scripts

Stored procedures

in Natural

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

Triggers

hooks for callbacks inside the server can be used.

yes

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

Multi-source replication
Source-replica replication

Multi-source replication

yes, but depending on the SQL-Server Edition

yes

by Federation

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Transaction concepts

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

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)

Pluggable authentication mechanisms

e.g. LDAP, HTTP

rights management via user accounts

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.