DBMS > Dolt vs. MySQL vs. SAP Advantage Database Server vs. Tkrzw vs. Transbase

System Properties Comparison Dolt vs. MySQL vs. SAP Advantage Database Server vs. Tkrzw vs. Transbase

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

Widely used open source RDBMS

Low-cost RDBMS with access to ISAM and FoxPro data structures

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	0.93
Rank	#194	Overall
	#90	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Score	0.05
Rank	#355	Overall
	#150	Relational DBMS

Website

github.com/dolthub/dolt
www.dolthub.com

www.mysql.com

www.sap.com/products/advantage-database-server.html

dbmx.net/tkrzw

www.transaction.de/en/products/transbase.html

Technical documentation

docs.dolthub.com

dev.mysql.com/doc

www.transaction.de/en/products/transbase/features.html

Developer

DoltHub Inc

Oracle

since 2010, originally MySQL AB, then Sun

Sybase, SAP

Mikio Hirabayashi

Transaction Software GmbH

Initial release

2018

1995

1993

2020

1987

Current release

9.0.0, July 2024

0.9.3, August 2020

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

Apache Version 2.0

commercial

free development license

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

C++

C and C++

Server operating systems

Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

Linux
macOS

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

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

CLI Client
HTTP REST

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

Delphi
Perl
PHP

C++
Java
Python
Ruby

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

currently in alpha release

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Multi-source replication
Source-replica replication

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

not for MyISAM storage engine

ACID

yes

Concurrency

Support for concurrent manipulation of data

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

caching of (temporary) tables can be configured

yes

using specific database classes

User concepts

Access control

Only one user is configurable, and must be specified in the config file at startup

Users with fine-grained authorization concept

no user groups or 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.