DBMS > Cubrid vs. GeoSpock vs. MySQL vs. SAP Advantage Database Server

System Properties Comparison Cubrid vs. GeoSpock vs. MySQL vs. SAP Advantage Database Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

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

Description

CUBRID is an open-source SQL-based relational database management system with object extensions for OLTP

Spatial and temporal data processing engine for extreme data scale

Widely used open source RDBMS

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

Primary database model

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

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

Score	0.97
Rank	#189	Overall
	#86	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

cubrid.com (korean)
cubrid.org (english)

geospock.com

www.mysql.com

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

Technical documentation

cubrid.org/manuals

dev.mysql.com/doc

Developer

CUBRID Corporation, CUBRID Foundation

GeoSpock

Oracle

since 2010, originally MySQL AB, then Sun

Sybase, SAP

Initial release

2008

1995

1993

Current release

11.0, January 2021

2.0, September 2019

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Implementation language

C, C++, Java

Java, Javascript

C and C++

Server operating systems

Linux
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

Data scheme

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

temporal, categorical

yes

SQL

Support of SQL

yes

ANSI SQL for query only (using Presto)

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

JDBC

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

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

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

Server-side scripts

Stored procedures

Java Stored Procedures

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
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

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

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per table

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.