DBMS > Apache Drill vs. Apache Druid vs. Microsoft SQL Server vs. Sadas Engine

System Properties Comparison Apache Drill vs. Apache Druid vs. Microsoft SQL Server vs. Sadas Engine

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

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Microsofts flagship relational DBMS

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

Document store
Relational DBMS

Relational DBMS
Time Series DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	2.28
Rank	#119	Overall
	#23	Document stores
	#56	Relational DBMS

Score	3.29
Rank	#95	Overall
	#49	Relational DBMS
	#7	Time Series DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	0.03
Rank	#379	Overall
	#156	Relational DBMS

Website

drill.apache.org

druid.apache.org

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

www.sadasengine.com

Technical documentation

drill.apache.org/docs

druid.apache.org/docs/latest/design

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

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Apache Software Foundation

Apache Software Foundation and contributors

Microsoft

SADAS s.r.l.

Initial release

2012

1989

2006

Current release

1.20.3, January 2023

29.0.1, April 2024

SQL Server 2022, November 2022

8.0

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache license v2

commercial

restricted free version is available

commercial

free trial version 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

Java

C++

Server operating systems

Linux
OS X
Windows

Linux
OS X
Unix

Linux
Windows

AIX
Linux
Windows

Data scheme

schema-free

yes

schema-less columns are supported

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

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL for querying

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
RESTful HTTP/JSON API

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

JDBC
ODBC
Proprietary protocol

Supported programming languages

C++

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

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

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

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

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

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

managed by 'Learn by Usage'

User concepts

Access control

Depending on the underlying data source

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

fine grained access rights according to SQL-standard

Access rights for users, groups and roles 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.