DBMS > MaxDB vs. MySQL vs. OrigoDB vs. PlanetScale vs. SAP Adaptive Server

System Properties Comparison MaxDB vs. MySQL vs. OrigoDB vs. PlanetScale vs. SAP Adaptive Server

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

A fully ACID in-memory object graph database

Scalable, distributed, serverless MySQL database platform built on top of Vitess

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

Primary database model

Relational DBMS

Key/Value like access via memcached API

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

with Boeing's Spatial Query Server

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

Score	2.26
Rank	#114	Overall
	#55	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	35.09
Rank	#25	Overall
	#17	Relational DBMS

Website

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

Technical documentation

maxdb.sap.com/documentation

dev.mysql.com/doc

origodb.com/docs

planetscale.com/docs

help.sap.com/docs/SAP_ASE

Developer

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

Oracle

since 2010, originally MySQL AB, then Sun

Robert Friberg et al

PlanetScale

SAP, Sybase

Initial release

1984

1995

2009

under the name LiveDB

2020

1987

Current release

7.9.10.12, February 2024

8.4.0, April 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

Open Source

commercial

Cloud-based only

Only available as a cloud service

yes

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

Linux
Windows

Docker
Linux
macOS

AIX
HP-UX
Linux
Solaris
Unix
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
WebDAV

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
HTTP API
LINQ

ADO.NET
JDBC
MySQL protocol
ODBC

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

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

.Net

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

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

proprietary syntax

Java and Transact-SQL

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

client side managed; servers are not synchronized

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

Source-replica replication

Multi-source replication
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 across shards
Immediate Consistency within a shard

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

depending on model

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

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

Write ahead log

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

Role based authorization

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.