DBMS > Apache Drill vs. BigchainDB vs. dBASE vs. MonetDB vs. SAP HANA

System Properties Comparison Apache Drill vs. BigchainDB vs. dBASE vs. MonetDB vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

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

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

dBase was one of the first databases with a development environment on PC's. Its latest version dBase V is still sold as dBase classic, which needs a DOS Emulation. The up-to-date product is dBase plus.

A relational database management system that stores data in columns

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Document store
Relational DBMS

Document store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

Score	1.72
Rank	#145	Overall
	#67	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.sap.com/products/hana.html

Technical documentation

drill.apache.org/docs

bigchaindb.readthedocs.io/en/latest

www.dbase.com/support/knowledgebase

www.monetdb.org/Documentation

help.sap.com/hana

Developer

Apache Software Foundation

Asthon Tate

MonetDB BV

SAP

Initial release

2012

2016

1979

2004

2010

Current release

1.20.3, January 2023

dBASE 2019, 2019

Dec2023 (11.49), December 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

AGPL v3

commercial

Open Source

Mozilla Public License 2.0

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Python

Server operating systems

Linux
OS X
Windows

Linux

DOS

dBase Classic
Windows

dBase Pro

FreeBSD
Linux
OS X
Solaris
Windows

Appliance or cloud-service

Data scheme

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.

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

SQL 2003 with some extensions

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

CLI Client
RESTful HTTP API

none

The IDE can access other DBMS or ODBC-sources.

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

JDBC
ODBC

Supported programming languages

C++

Go
Haskell
Java
JavaScript
Python
Ruby

dBase proprietary IDE

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

Server-side scripts

Stored procedures

user defined functions

The IDE can access stored procedures in other database systems.

yes, in SQL, C, R

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding via remote tables

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

Source-replica replication available in experimental status

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

not for dBase internal data, but IDE does support transactions when accessing external DBMS

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes,with MongoDB ord RethinkDB

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

User concepts

Access control

Depending on the underlying data source

yes

Access rights for users and roles

fine grained access rights according to SQL-standard

yes

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.