DBMS > Faircom DB vs. mSQL vs. Quasardb vs. SAP HANA

System Properties Comparison Faircom DB vs. mSQL vs. Quasardb vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

mSQL (Mini SQL) is a simple and lightweight RDBMS

Distributed, high-performance timeseries database

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

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.29
Rank	#304	Overall
	#43	Key-value stores
	#136	Relational DBMS

Score	1.27
Rank	#169	Overall
	#76	Relational DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.faircom.com/products/faircom-db

hughestech.com.au/products/msql

quasar.ai

www.sap.com/products/hana.html

Technical documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

doc.quasar.ai/master

help.sap.com/hana

Developer

FairCom Corporation

Hughes Technologies

quasardb

SAP

Initial release

1979

1994

2009

2010

Current release

V12, November 2020

4.4, October 2021

3.14.1, January 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

free licenses can be provided

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

commercial

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

ANSI C, C++

C++

Server operating systems

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

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

BSD
Linux
OS X
Windows

Appliance or cloud-service

Data scheme

schema free, schema optional, schema required, partial schema,

yes

schema-free

yes

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

yes

integer and binary

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.

Secondary indexes

yes

with tags

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

A subset of ANSI SQL is implemented

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

SQL-like query language

yes

APIs and other access methods

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

JDBC
ODBC

HTTP API

JDBC
ODBC

Supported programming languages

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

none

Sharding

consistent hashing

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

none

Source-replica replication with selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Yes, tunable from durable to delayed durability to in-memory

yes

by using LevelDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

yes

User concepts

Access control

Fine grained access rights according to SQL-standard with additional protections for files

Cryptographically strong user authentication and audit trail

yes

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.