DBMS > Microsoft SQL Server vs. mSQL vs. SiteWhere vs. Sphinx vs. STSdb

System Properties Comparison Microsoft SQL Server vs. mSQL vs. SiteWhere vs. Sphinx vs. STSdb

Editorial information provided by DB-Engines

Name

Description

Microsofts flagship relational DBMS

mSQL (Mini SQL) is a simple and lightweight RDBMS

M2M integration platform for persisting/querying time series data

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	1.27
Rank	#169	Overall
	#76	Relational DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Website

www.microsoft.com/en-us/sql-server

hughestech.com.au/products/msql

github.com/sitewhere/sitewhere

sphinxsearch.com

github.com/STSSoft/STSdb4

Technical documentation

learn.microsoft.com/en-US/sql/sql-server

sitewhere1.sitewhere.io/index.html

sphinxsearch.com/docs

Developer

Microsoft

Hughes Technologies

SiteWhere

Sphinx Technologies Inc.

STS Soft SC

Initial release

1989

1994

2010

2001

2011

Current release

SQL Server 2022, November 2022

4.4, October 2021

3.5.1, February 2023

4.0.8, September 2015

License

Commercial or Open Source

commercial

restricted free version is available

commercial

free licenses can be provided

Open Source

Common Public Attribution License Version 1.0

Open Source

GPL version 2, commercial licence available

Open Source

GPLv2, commercial license available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

C++

Java

C++

Server operating systems

Linux
Windows

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

Linux
OS X
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Windows

Data scheme

yes

predefined scheme

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

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

SQL-like query language (SphinxQL)

APIs and other access methods

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

JDBC
ODBC

HTTP REST

Proprietary protocol

.NET Client API

Supported programming languages

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

C
C++
Delphi
Java
Perl
PHP
Tcl

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C#
Java

Server-side scripts

Stored procedures

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

tables can be distributed across several files (horizontal partitioning); sharding through federation

none

Sharding

based on HBase

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, but depending on the SQL-Server Edition

none

selectable replication factor

based on HBase

none

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

Users with fine-grained authorization concept

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.