DBMS > dBASE vs. IRONdb vs. MonetDB vs. SAP HANA

System Properties Comparison dBASE vs. IRONdb vs. MonetDB vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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 distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

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

Relational DBMS

Time Series DBMS

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	9.70
Rank	#44	Overall
	#28	Relational DBMS

Score	1.72
Rank	#141	Overall
	#64	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.dbase.com

www.circonus.com/solutions/time-series-database/

www.monetdb.org

www.sap.com/products/hana.html

Technical documentation

www.dbase.com/support/knowledgebase

docs.circonus.com/irondb/category/getting-started

www.monetdb.org/Documentation

help.sap.com/hana

Developer

Asthon Tate

Circonus LLC.

MonetDB BV

SAP

Initial release

1979

2017

2004

2010

Current release

dBASE 2019, 2019

V0.10.20, January 2018

Dec2023 (11.49), December 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

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

C and C++

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Appliance or cloud-service

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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-like query language (Circonus Analytics Query Language: CAQL)

yes

SQL 2003 with some extensions

yes

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

HTTP API

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

JDBC
ODBC

Supported programming languages

dBase proprietary IDE

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

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

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

yes, in Lua

yes, in SQL, C, R

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic, metric affinity per node

Sharding via remote tables

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

configurable replication factor, datacenter aware

none

Source-replica replication available in experimental status

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency per node, eventual consistency across nodes

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

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

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.