DBMS > Apache Drill vs. Microsoft SQL Server vs. Solr vs. Sphinx

System Properties Comparison Apache Drill vs. Microsoft SQL Server vs. Solr vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Microsofts flagship relational DBMS

A widely used distributed, scalable search engine based on Apache Lucene

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

Primary database model

Document store
Relational DBMS

Relational DBMS

Search engine

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Spatial DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

drill.apache.org

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

solr.apache.org

sphinxsearch.com

Technical documentation

drill.apache.org/docs

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

solr.apache.org/resources.html

sphinxsearch.com/docs

Developer

Apache Software Foundation

Microsoft

Apache Software Foundation

Sphinx Technologies Inc.

Initial release

2012

1989

2006

2001

Current release

1.20.3, January 2023

SQL Server 2022, November 2022

9.6.0, April 2024

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

restricted free version is available

Open Source

Apache Version 2

Open Source

GPL version 2, commercial licence 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.

Implementation language

C++

Java

C++

Server operating systems

Linux
OS X
Windows

Linux
Windows

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

yes

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

yes

full-text index on all search fields

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

Solr Parallel SQL Interface

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

Java API
RESTful HTTP/JSON API

Proprietary protocol

Supported programming languages

C++

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

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

user defined functions

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

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

yes, but depending on the SQL-Server Edition

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

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.

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

fine grained access rights according to SQL-standard

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.