DBMS > FatDB vs. MySQL vs. QuestDB vs. SAP Advantage Database Server

System Properties Comparison FatDB vs. MySQL vs. QuestDB vs. SAP Advantage Database Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

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

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Widely used open source RDBMS

A high performance open source SQL database for time series data

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

Primary database model

Document store
Key-value store

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	2.81
Rank	#98	Overall
	#7	Time Series DBMS

Website

www.mysql.com

questdb.io

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

Technical documentation

dev.mysql.com/doc

questdb.io/docs

Developer

FatCloud

Oracle

since 2010, originally MySQL AB, then Sun

QuestDB Technology Inc

Sybase, SAP

Initial release

2012

1995

2014

1993

Current release

9.0.0, July 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache 2.0

commercial

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

Java (Zero-GC), C++, Rust

Server operating systems

Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS
Windows

Linux
Windows

Data scheme

schema-free

yes

schema-free via InfluxDB Line Protocol

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

Via inetgration in SQL Server

yes

with proprietary extensions

SQL with time-series extensions

yes

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

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

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

Delphi
Perl
PHP

Server-side scripts

Stored procedures

yes

via applications

yes

proprietary syntax

yes

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning (by timestamps)

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

Source-replica replication with eventual consistency

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

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 for single-table writes

ACID

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

through memory mapped files

caching of (temporary) tables can be configured

User concepts

Access control

Can implement custom security layer via applications

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

News

Combine Java and Rust Code Coverage in a Polyglot Project
10 September 2024

Weather data visualization and forecasting with QuestDB, Kafka and Grafana
4 September 2024

Building a new vector based storage model
22 August 2024

Calibrating VWAP executions with QuestDB and Grafana
16 August 2024

Write Time: a call for community writers
13 August 2024

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.