DBMS > dBASE vs. MySQL vs. Splunk vs. STSdb

System Properties Comparison dBASE vs. MySQL vs. Splunk vs. STSdb

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

Analytics Platform for Big Data

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Relational DBMS

Key/Value like access via memcached API

Search engine

Key-value store

Secondary database models

Document store
Spatial 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	93.02
Rank	#13	Overall
	#2	Search engines

Score	0.03
Rank	#365	Overall
	#54	Key-value stores

Website

www.dbase.com

www.mysql.com

www.splunk.com

github.com/STSSoft/STSdb4

Technical documentation

www.dbase.com/support/knowledgebase

dev.mysql.com/doc

docs.splunk.com/Documentation/Splunk

Developer

Asthon Tate

Oracle

since 2010, originally MySQL AB, then Sun

Splunk Inc.

STS Soft SC

Initial release

1979

1995

2003

2011

Current release

dBASE 2019, 2019

9.0.0, July 2024

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Limited free edition and free developer edition available

Open Source

GPLv2, commercial license available

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

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

SQL

Support of SQL

yes

with proprietary extensions

Splunk Search Processing Language for search commands

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

.NET Client API

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#
Java
JavaScript
PHP
Python
Ruby

C#
Java

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

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

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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

Access rights for users and roles

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.