DBMS > mSQL vs. PostGIS vs. Postgres-XL vs. Snowflake vs. Sphinx

System Properties Comparison mSQL vs. PostGIS vs. Postgres-XL vs. Snowflake vs. Sphinx

Editorial information provided by DB-Engines

Name

Description

mSQL (Mini SQL) is a simple and lightweight RDBMS

Spatial extension of PostgreSQL

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Cloud-based data warehousing service for structured and semi-structured data

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

Primary database model

Secondary database models

Relational DBMS

Document store
Spatial DBMS

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

Score	1.27
Rank	#169	Overall
	#76	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

hughestech.com.au/products/msql

Technical documentation

postgis.net/documentation

www.postgres-xl.org/documentation

docs.snowflake.net/manuals/index.html

sphinxsearch.com/docs

Developer

Hughes Technologies

Snowflake Computing Inc.

Sphinx Technologies Inc.

Initial release

1994

2005

2014

since 2012, originally named StormDB

2014

2001

Current release

4.4, October 2021

3.4.2, February 2024

10 R1, October 2018

3.5.1, February 2023

License

Commercial or Open Source

commercial

free licenses can be provided

Open Source

GPL v2.0

Open Source

Mozilla public license

commercial

Open Source

GPL version 2, commercial licence available

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

Server operating systems

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

Linux
macOS

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

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

XML type, but no XML query functionality

yes

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

A subset of ANSI SQL is implemented

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

yes

distributed, parallel query execution

yes

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC

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

CLI Client
JDBC
ODBC

Proprietary protocol

Supported programming languages

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

yes

based on PostgreSQL

horizontal partitioning

yes

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

based on PostgreSQL

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

MVCC

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.

In-memory capabilities

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

User concepts

Access control

yes

based on PostgreSQL

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.