DBMS > dBASE vs. EXASOL vs. Firebird vs. OpenEdge vs. Snowflake

System Properties Comparison dBASE vs. EXASOL vs. Firebird vs. OpenEdge vs. Snowflake

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.

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Firebird is an open source RDBMS forked from Borland's InterBase

Application development environment with integrated database management system

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Relational DBMS

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

Score	9.70
Rank	#44	Overall
	#28	Relational DBMS

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	20.50
Rank	#30	Overall
	#18	Relational DBMS

Score	3.45
Rank	#85	Overall
	#46	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.dbase.com

www.exasol.com

www.firebirdsql.org

www.progress.com/openedge

www.snowflake.com

Technical documentation

www.dbase.com/support/knowledgebase

www.exasol.com/resources

www.firebirdsql.org/en/reference-manuals

documentation.progress.com/output/ua/OpenEdge_latest

docs.snowflake.net/manuals/index.html

Developer

Asthon Tate

Exasol

Firebird Foundation

Progress Software Corporation

Snowflake Computing Inc.

Initial release

1979

2000

As fork of Borland's InterBase

1984

2014

Current release

dBASE 2019, 2019

5.0.0, January 2024

OpenEdge 12.2, March 2020

License

Commercial or Open Source

commercial

Open Source

Initial Developer's Public License

commercial

Cloud-based only

Only available as a cloud service

yes

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

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

AIX
HP-UX
Linux
Solaris
Windows

hosted

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

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

SQL

Support of SQL

yes

close to SQL 92

yes

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

.Net
JDBC
ODBC
WebSocket

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

dBase proprietary IDE

Java
Lua
Python
R

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

Progress proprietary ABL (Advanced Business Language)

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

user defined functions

PSQL

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

horizontal partitioning

since Version 11.4

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Features a multi-generational MVCC architecture, readers do not block writers

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

Access rights for users, groups and roles according to SQL-standard

Users with fine-grained authorization concept

Users and groups

Users with fine-grained authorization concept, user roles and pluggable authentication

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.