DBMS > dBASE vs. MySQL vs. RocksDB vs. Teradata

System Properties Comparison dBASE vs. MySQL vs. RocksDB vs. Teradata

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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.

Widely used open source RDBMS

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Relational DBMS

Key/Value like access via memcached API

Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	9.16
Rank	#43	Overall
	#27	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	2.84
Rank	#97	Overall
	#16	Key-value stores

Score	41.47
Rank	#22	Overall
	#15	Relational DBMS

Website

Technical documentation

www.dbase.com/support/knowledgebase

dev.mysql.com/doc

github.com/facebook/rocksdb/wiki

docs.teradata.com

Developer

Asthon Tate

Oracle

since 2010, originally MySQL AB, then Sun

Facebook, Inc.

Teradata

Initial release

1979

1995

2013

1984

Current release

dBASE 2019, 2019

9.0.0, July 2024

9.4.0, June 2024

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

BSD

commercial

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

C++

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

FreeBSD
Linux
OS X
Solaris
Windows

Linux

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.

yes

Secondary indexes

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL 2016 + extensions

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

ADO.NET
JDBC
ODBC
Proprietary native API

C++ API
Java API

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

dBase proprietary IDE

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Go
Java
Perl
Python
Ruby

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

yes

proprietary syntax

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

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

not for MyISAM storage engine

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

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.