DBMS > Linter vs. Microsoft SQL Server vs. Percona Server for MySQL vs. Sphinx vs. Valentina Server

System Properties Comparison Linter vs. Microsoft SQL Server vs. Percona Server for MySQL vs. Sphinx vs. Valentina Server

Editorial information provided by DB-Engines

Name

Description

RDBMS for high security requirements

Microsofts flagship relational DBMS

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

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

Object-relational database and reports server

Primary database model

Relational DBMS

Search engine

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	2.03
Rank	#122	Overall
	#57	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

linter.ru

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

www.percona.com/software/mysql-database/percona-server

sphinxsearch.com

www.valentina-db.net

Technical documentation

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

www.percona.com/downloads/Percona-Server-LATEST

sphinxsearch.com/docs

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

relex.ru

Microsoft

Percona

Sphinx Technologies Inc.

Paradigma Software

Initial release

1990

1989

2008

2001

1999

Current release

SQL Server 2022, November 2022

8.0.36-28, 2024

3.5.1, February 2023

5.7.5

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

GPL version 2

Open Source

GPL version 2, commercial licence available

commercial

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.

Implementation language

C and C++

C++

C and C++

C++

Server operating systems

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux
Windows

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X
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

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

yes

APIs and other access methods

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

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

ADO.NET
JDBC
ODBC

Proprietary protocol

ODBC

Supported programming languages

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

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

Ada
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

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

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

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

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication
XtraDB Cluster

none

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

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

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.