DBMS > MySQL vs. Qdrant vs. SAP SQL Anywhere vs. ToroDB vs. Valentina Server

System Properties Comparison MySQL vs. Qdrant vs. SAP SQL Anywhere vs. ToroDB vs. Valentina Server

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Widely used open source RDBMS

A high-performance vector database with neural network or semantic-based matching

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Object-relational database and reports server

Primary database model

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

www.mysql.com

github.com/qdrant/qdrant
qdrant.tech

www.sap.com/products/technology-platform/sql-anywhere.html

github.com/torodb/server

www.valentina-db.net

Technical documentation

dev.mysql.com/doc

qdrant.tech/documentation

help.sap.com/docs/SAP_SQL_Anywhere

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Oracle

since 2010, originally MySQL AB, then Sun

Qdrant

SAP

formerly Sybase

8Kdata

Paradigma Software

Initial release

1995

2021

1992

2016

1999

Current release

8.4.0, April 2024

17, July 2015

5.7.5

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 2.0

commercial

Open Source

AGPL-V3

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.

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

Rust

Java

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

Docker
Linux
macOS
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

All OS with a Java 7 VM

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

yes

string, integer, double, boolean, date, object_id

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

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

ADO.NET
HTTP API
JDBC
ODBC

ODBC

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

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

yes

proprietary syntax

yes, in C/C++, Java, .Net or Perl

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Collection-level replication

Source-replica replication

Database mirroring

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

Eventual Consistency, tunable consistency

Immediate Consistency

Eventual 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

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

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

Key-based authentication

fine grained access rights according to SQL-standard

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.