DBMS > dBASE vs. Interbase vs. Microsoft Azure Data Explorer vs. MySQL vs. searchxml

System Properties Comparison dBASE vs. Interbase vs. Microsoft Azure Data Explorer vs. MySQL vs. searchxml

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.

Light-weight proven RDBMS

originally from Borland

Fully managed big data interactive analytics platform

Widely used open source RDBMS

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Relational DBMS

column oriented

Relational DBMS

Key/Value like access via memcached API

Native XML DBMS
Search engine

Secondary database models

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

Document store
Spatial DBMS

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

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Website

www.dbase.com

www.embarcadero.com/products/interbase

azure.microsoft.com/services/data-explorer

www.mysql.com

www.searchxml.net/category/products

Technical documentation

www.dbase.com/support/knowledgebase

docs.embarcadero.com/products/interbase

docs.microsoft.com/en-us/azure/data-explorer

dev.mysql.com/doc

www.searchxml.net/support/handouts

Developer

Asthon Tate

Embarcadero

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

informationpartners gmbh

Initial release

1979

1984

2019

1995

2015

Current release

dBASE 2019, 2019

InterBase 2020, December 2019

cloud service with continuous releases

8.4.0, April 2024

1.0

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

C++

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

Android
iOS
Linux
OS X
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Windows

Data scheme

yes

Fixed schema with schema-less datatypes (dynamic)

yes

schema-free

Typing

predefined data types such as float or date

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types

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.

export as XML data possible

yes

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

Kusto Query Language (KQL), SQL subset

yes

with proprietary extensions

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

ADO.NET
JDBC
ODBC

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

dBase proprietary IDE

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

yes

Interbase procedure and trigger language

Yes, possible languages: KQL, Python, R

yes

proprietary syntax

yes

on the application server

Triggers

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Interbase Change Views

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication
Source-replica replication

yes

sychronisation to multiple collections

MapReduce

Offers an API for user-defined Map/Reduce methods

Spark connector (open source): github.com/Azure/azure-kusto-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

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

not for MyISAM storage engine

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

table locks or row locks depending on storage engine

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

fine grained access rights according to SQL-standard

Azure Active Directory Authentication

Users with fine-grained authorization concept

no user groups or roles

Domain, group and role-based access control at the document level and for application services

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.