DBMS > dBASE vs. FatDB vs. RocksDB vs. SQream DB

System Properties Comparison dBASE vs. FatDB vs. RocksDB vs. SQream DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the 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 .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Relational DBMS

Document store
Key-value store

Key-value store

Relational DBMS

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

Score	9.70
Rank	#44	Overall
	#28	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.74
Rank	#224	Overall
	#103	Relational DBMS

Website

www.dbase.com

rocksdb.org

sqream.com

Technical documentation

www.dbase.com/support/knowledgebase

github.com/facebook/rocksdb/wiki

docs.sqream.com

Developer

Asthon Tate

FatCloud

Facebook, Inc.

SQream Technologies

Initial release

1979

2012

2013

2017

Current release

dBASE 2019, 2019

9.2.1, May 2024

2022.1.6, December 2022

License

Commercial or Open Source

commercial

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

C++, CUDA, Haskell, Java, Scala

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

Windows

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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

Via inetgration in SQL Server

yes

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

C++ API
Java API

.Net
JDBC
ODBC

Supported programming languages

dBase proprietary IDE

C
C++
Go
Java
Perl
Python
Ruby

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

yes

via applications

user defined functions in Python

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

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

yes

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

Can implement custom security layer via applications

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.