DBMS > MaxDB vs. MySQL vs. SAP Adaptive Server vs. YottaDB

System Properties Comparison MaxDB vs. MySQL vs. SAP Adaptive Server vs. YottaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A robust and reliable RDBMS optimized to run all major SAP solutions

Widely used open source RDBMS

The SAP (Sybase) Adaptive Server Enterprise (ASE) is an enterprise-class RDBMS

A fast and solid embedded Key-value store

Primary database model

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Key-value store

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

with Boeing's Spatial Query Server

Relational DBMS

using the Octo plugin

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

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	36.31
Rank	#25	Overall
	#17	Relational DBMS

Score	0.20
Rank	#317	Overall
	#47	Key-value stores

Website

maxdb.sap.com

www.mysql.com

www.sap.com/products/technology-platform/sybase-ase.html

yottadb.com

Technical documentation

maxdb.sap.com/documentation

dev.mysql.com/doc

help.sap.com/docs/SAP_ASE

yottadb.com/resources/documentation

Developer

SAP, acquired from Software AG (Adabas-D) in 1997

Oracle

since 2010, originally MySQL AB, then Sun

SAP, Sybase

YottaDB, LLC

Initial release

1984

1995

1987

2001

Current release

7.9.10.12, February 2024

8.3.0, January 2024

16.0

License

Commercial or Open Source

commercial

Limited community edition free

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

AGPL 3.0

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

C and C++

Server operating systems

AIX
HP-UX
Linux
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Unix
Windows

Docker
Linux

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

yes

with proprietary extensions

yes

by using the Octo plugin

APIs and other access methods

ADO.NET
JDBC
ODBC
WebDAV

ADO.NET
JDBC
ODBC
Proprietary native API

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

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

.Net
C#
Java
Perl
PHP
Python

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

C
C++
Cobol
Java
Java
Perl
PHP
Python

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

yes

proprietary syntax

Java and Transact-SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

yes

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

optimistic locking

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

Users and groups based on OS-security mechanisms

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.