DBMS > Apache Impala vs. dBASE vs. Microsoft SQL Server vs. TerarkDB

System Properties Comparison Apache Impala vs. dBASE vs. Microsoft SQL Server vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

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.

Microsofts flagship relational DBMS

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS

Key-value store

Secondary database models

Document store

Document store
Graph DBMS
Spatial DBMS

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

Score	14.03
Rank	#40	Overall
	#24	Relational DBMS

Score	11.18
Rank	#44	Overall
	#28	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	0.04
Rank	#377	Overall
	#58	Key-value stores

Website

impala.apache.org

www.dbase.com

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

github.com/bytedance/terarkdb

Technical documentation

impala.apache.org/impala-docs.html

www.dbase.com/support/knowledgebase

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

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Asthon Tate

Microsoft

ByteDance, originally Terark

Initial release

2013

1979

1989

2016

Current release

4.1.0, June 2022

dBASE 2019, 2019

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

restricted free version is available

commercial

restricted open source version 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++

Server operating systems

Linux

DOS

dBase Classic
Windows

dBase Pro

Linux
Windows

Data scheme

yes

schema-free

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

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC

none

The IDE can access other DBMS or ODBC-sources.

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

C++ API
Java API

Supported programming languages

All languages supporting JDBC/ODBC

dBase proprietary IDE

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

C++
Java

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

The IDE can access stored procedures in other database systems.

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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

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, groups and roles

based on Apache Sentry and Kerberos

Access rights for users and roles

fine grained access rights 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.