DBMS > Adabas vs. Drizzle vs. EJDB vs. Microsoft SQL Server vs. Rockset

System Properties Comparison Adabas vs. Drizzle vs. EJDB vs. Microsoft SQL Server vs. Rockset

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.

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Microsofts flagship relational DBMS

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Relational DBMS
Search engine

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

Score	3.58
Rank	#91	Overall
	#1	Multivalue DBMS

Score	0.30
Rank	#294	Overall
	#44	Document stores

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	0.84
Rank	#209	Overall
	#35	Document stores

Website

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

github.com/Softmotions/ejdb

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

rockset.com

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

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

docs.rockset.com

Developer

Software AG

Drizzle project, originally started by Brian Aker

Softmotions

Microsoft

Rockset

Initial release

1971

2008

2012

1989

2019

Current release

7.2.4, September 2012

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

GPLv2

commercial

restricted free version is available

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

Server operating systems

BS2000
Linux
Unix
Windows
z/OS
z/VSE

FreeBSD
Linux
OS X

server-less

Linux
Windows

hosted

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

dynamic typing

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

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

yes

with add-on product Adabas SQL Gateway

yes

with proprietary extensions

yes

Read-only SQL queries, including JOINs

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

in-process shared library

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

HTTP REST

Supported programming languages

Natural

C
C++
Java
PHP

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

Go
Java
JavaScript (Node.js)
Python

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

none

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

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with add-on product Event Replicator

Multi-source replication
Source-replica replication

none

yes, but depending on the SQL-Server Edition

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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

fine grained access rights according to SQL-standard

Access rights for users and organizations can be defined via Rockset console

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.