DBMS > dBASE vs. Quasardb vs. SiriDB vs. Spark SQL vs. SQLite

System Properties Comparison dBASE vs. Quasardb vs. SiriDB vs. Spark SQL vs. SQLite

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.

Distributed, high-performance timeseries database

Open Source Time Series DBMS

Spark SQL is a component on top of 'Spark Core' for structured data processing

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

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

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

www.dbase.com/support/knowledgebase

doc.quasar.ai/master

docs.siridb.com

spark.apache.org/docs/latest/sql-programming-guide.html

www.sqlite.org/docs.html

Developer

Asthon Tate

quasardb

Cesbit

Apache Software Foundation

Dwayne Richard Hipp

Initial release

1979

2009

2017

2014

2000

Current release

dBASE 2019, 2019

3.14.1, January 2024

3.5.0 ( 2.13), September 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

MIT License

Open Source

Apache 2.0

Open Source

Public Domain

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

Scala

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

BSD
Linux
OS X
Windows

Linux

Linux
OS X
Windows

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

integer and binary

yes

Numeric data

yes

not rigid because of 'dynamic typing' concept.

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

with tags

yes

SQL

Support of SQL

SQL-like query language

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

HTTP API

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

dBase proprietary IDE

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

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

Java
Python
R
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

consistent hashing

Sharding

yes, utilizing Spark Core

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication with selectable replication factor

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

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

via file-system locks

Durability

Support for making data persistent

yes

by using LevelDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

yes

User concepts

Access control

Access rights for users and roles

Cryptographically strong user authentication and audit trail

simple rights management via user accounts

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.