DBMS > CockroachDB vs. dBASE vs. SQLite vs. STSdb

System Properties Comparison CockroachDB vs. dBASE vs. SQLite vs. STSdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

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 embeddable, in-process RDBMS

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Relational DBMS

Key-value store

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

Score	4.74
Rank	#67	Overall
	#36	Relational DBMS

Score	9.16
Rank	#43	Overall
	#27	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

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

Website

www.cockroachlabs.com

www.dbase.com

www.sqlite.org

github.com/STSSoft/STSdb4

Technical documentation

www.cockroachlabs.com/docs

www.dbase.com/support/knowledgebase

www.sqlite.org/docs.html

Developer

Cockroach Labs

Asthon Tate

Dwayne Richard Hipp

STS Soft SC

Initial release

2015

1979

2000

2011

Current release

24.1.0, May 2024

dBASE 2019, 2019

3.46.1 (13 August 2024), August 2024

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

Open Source

Public Domain

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

Server operating systems

Linux
macOS
Windows

DOS

dBase Classic
Windows

dBase Pro

server-less

Windows

Data scheme

dynamic schema

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

yes

SQL

Support of SQL

yes, wire compatible with PostgreSQL

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

none

The IDE can access other DBMS or ODBC-sources.

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

.NET Client API

Supported programming languages

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

dBase proprietary IDE

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

C#
Java

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

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

none

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

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

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

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

Role-based access control

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.