DBMS > dBASE vs. Drizzle vs. Microsoft SQL Server vs. Splice Machine

System Properties Comparison dBASE vs. Drizzle vs. Microsoft SQL Server vs. Splice Machine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines 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.

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Microsofts flagship relational DBMS

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

Primary database model

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	10.34
Rank	#44	Overall
	#28	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.54
Rank	#250	Overall
	#114	Relational DBMS

Website

www.dbase.com

www.microsoft.com/en-us/sql-server

splicemachine.com

Technical documentation

www.dbase.com/support/knowledgebase

learn.microsoft.com/en-US/sql/sql-server

splicemachine.com/how-it-works

Developer

Asthon Tate

Drizzle project, originally started by Brian Aker

Microsoft

Splice Machine

Initial release

1979

2008

1989

2014

Current release

dBASE 2019, 2019

7.2.4, September 2012

SQL Server 2022, November 2022

3.1, March 2021

License

Commercial or Open Source

commercial

Open Source

GNU GPL

commercial

restricted free version is available

Open Source

AGPL 3.0, 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

C++

Java

Server operating systems

DOS

dBase Classic
Windows

dBase Pro

FreeBSD
Linux
OS X

Linux
Windows

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

none

The IDE can access other DBMS or ODBC-sources.

JDBC

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

JDBC
Native Spark Datasource
ODBC

Supported programming languages

dBase proprietary IDE

C
C++
Java
PHP

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

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

Server-side scripts

Stored procedures

The IDE can access stored procedures in other database systems.

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes

Java

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

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.