DBMS > dBASE vs. EXASOL vs. Google BigQuery vs. Microsoft Access vs. Splice Machine

System Properties Comparison dBASE vs. EXASOL vs. Google BigQuery vs. Microsoft Access vs. Splice Machine

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.

Large scale data warehouse service with append-only tables

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Primary database model

Relational DBMS

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

Score	9.16
Rank	#43	Overall
	#27	Relational DBMS

Score	1.66
Rank	#138	Overall
	#64	Relational DBMS

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	93.76
Rank	#12	Overall
	#8	Relational DBMS

Score	0.54
Rank	#244	Overall
	#114	Relational DBMS

Website

www.dbase.com

www.exasol.com

cloud.google.com/bigquery

www.microsoft.com/en-us/microsoft-365/access

splicemachine.com

Technical documentation

www.dbase.com/support/knowledgebase

www.exasol.com/resources

cloud.google.com/bigquery/docs

developer.microsoft.com/en-us/access

splicemachine.com/how-it-works

Developer

Asthon Tate

Exasol

Google

Microsoft

Splice Machine

Initial release

1979

2000

2010

1992

2014

Current release

dBASE 2019, 2019

1902 (16.0.11328.20222), March 2019

3.1, March 2021

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

AGPL 3.0, commercial license available

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

Java

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

hosted

Windows

Not a real database server, but making use of DLLs

Linux
OS X
Solaris
Windows

Data scheme

yes

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.

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

.Net
JDBC
ODBC
WebSocket

RESTful HTTP/JSON API

ADO.NET
DAO
ODBC
OLE DB

JDBC
Native Spark Datasource
ODBC

Supported programming languages

dBase proprietary IDE

Java
Lua
Python
R

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

user defined functions

in JavaScript

yes

since Access 2010 using the ACE-engine

yes

Java

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Yes, via Full Spark 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

Since BigQuery is designed for querying data

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

but no files for transaction logging

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

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

a simple user-level security was built in till version Access 2003

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

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.