DBMS > Microsoft Azure SQL Database vs. Microsoft SQL Server vs. ScyllaDB vs. Sphinx

System Properties Comparison Microsoft Azure SQL Database vs. Microsoft SQL Server vs. ScyllaDB vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering with high compatibility to Microsoft SQL Server

Microsofts flagship relational DBMS

Cassandra and DynamoDB compatible wide column store

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

Primary database model

Relational DBMS

Wide column store

Search engine

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Key-value store

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

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	4.75
Rank	#68	Overall
	#5	Wide column stores

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

azure.microsoft.com/en-us/products/azure-sql/database

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

www.scylladb.com

sphinxsearch.com

Technical documentation

docs.microsoft.com/en-us/azure/azure-sql

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

docs.scylladb.com

sphinxsearch.com/docs

Developer

Microsoft

ScyllaDB

Sphinx Technologies Inc.

Initial release

2010

1989

2015

2001

Current release

V12

SQL Server 2022, November 2022

ScyllaDB Open Source 5.4.1, January 2024

3.5.1, February 2023

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

Open Source (AGPL), commercial license available

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.

Scylla Cloud: Create real-time applications that run at global scale with Scylla Cloud, the industry’s most powerful NoSQL DBaaS

Implementation language

C++

Server operating systems

hosted

Linux
Windows

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

schema-free

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

cluster global secondary indices

yes

full-text index on all search fields

SQL

Support of SQL

yes

SQL-like DML and DDL statements (CQL)

SQL-like query language (SphinxQL)

APIs and other access methods

ADO.NET
JDBC
ODBC

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

Proprietary protocol (CQL)

compatible with CQL (Cassandra Query Language, an SQL-like language)
RESTful HTTP API (DynamoDB compatible)
Thrift

Proprietary protocol

Supported programming languages

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

For CQL interface: C#, C++, Clojure, Erlang, Go, Haskell, Java, JavaScript, Node.js, Perl, PHP, Python, Ruby, Rust, Scala
For DynamoDB interface: .Net, ColdFusion, Erlang, Groovy, Java, JavaScript, Perl, PHP, Python, Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

Transact SQL

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

yes, Lua

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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, with always 3 replicas available

yes, but depending on the SQL-Server Edition

selectable replication factor

Representation of geographical distribution of servers is possible

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Tunable Consistency

can be individually decided for each write operation

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomicity and isolation are supported for single operations

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.

yes

in-memory tables

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per object

More information provided by the system vendor

Specific characteristics

ScyllaDB is engineered to deliver predictable performance at scale. It’s adopted...
» more

Competitive advantages

Highly-performant (efficiently utilizes full resources of a node and network; millions...
» more

Typical application scenarios

ScyllaDB is ideal for applications that require high throughput and low latency at...
» more

Key customers

Discord, Epic Games, Expedia, Zillow, Comcast, Disney+ Hotstar, Samsung, ShareChat,...
» more

Market metrics

ScyllaDB typically offers ~75% total cost of ownership savings, with ~5X higher throughput...
» more

Licensing and pricing models

ScyllaDB Open Source - free open source software (AGPL) ScyllaDB Enterprise - subscription-based...
» more

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.