DBMS > Cubrid vs. mSQL vs. SAP HANA vs. Sphinx vs. TimescaleDB

System Properties Comparison Cubrid vs. mSQL vs. SAP HANA vs. Sphinx vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

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

mSQL (Mini SQL) is a simple and lightweight RDBMS

In-memory, column based data store. Available as appliance or cloud service

Open source search engine for searching in data from different sources, e.g. relational databases

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Relational DBMS

Search engine

Time Series DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Relational DBMS

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

Score	1.20
Rank	#169	Overall
	#78	Relational DBMS

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

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

hughestech.com.au/products/msql

www.sap.com/products/hana.html

sphinxsearch.com

www.timescale.com

Technical documentation

cubrid.org/manuals

help.sap.com/hana

sphinxsearch.com/docs

docs.timescale.com

Developer

CUBRID Corporation, CUBRID Foundation

Hughes Technologies

SAP

Sphinx Technologies Inc.

Timescale

Initial release

2008

1994

2010

2001

2017

Current release

11.0, January 2021

4.4, October 2021

2.0 SPS07 (April 4, 2023), April 2023

3.5.1, February 2023

2.15.0, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

free licenses can be provided

commercial

Open Source

GPL version 2, commercial licence available

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C, C++, Java

C++

Server operating systems

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Appliance or cloud-service

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

full-text index on all search fields

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

SQL-like query language (SphinxQL)

yes

full PostgreSQL SQL syntax

APIs and other access methods

ADO.NET
JDBC
ODBC
OLE DB

JDBC
ODBC

Proprietary protocol

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

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

C
C++
Delphi
Java
Perl
PHP
Tcl

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

Java Stored Procedures

SQLScript, R

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

Partitioning is done manually, search queries against distributed index is supported

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

yes

none

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

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

yes

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.