DBMS > Apache Drill vs. JaguarDB vs. Microsoft SQL Server vs. Snowflake

System Properties Comparison Apache Drill vs. JaguarDB vs. Microsoft SQL Server vs. Snowflake

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

Performant, highly scalable DBMS for AI and IoT applications

Microsofts flagship relational DBMS

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Document store
Relational DBMS

Key-value store
Vector 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.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#14	Vector DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

drill.apache.org

www.jaguardb.com

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

www.snowflake.com

Technical documentation

drill.apache.org/docs

www.jaguardb.com/support.html

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

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

DataJaguar, Inc.

Microsoft

Snowflake Computing Inc.

Initial release

2012

2015

1989

2014

Current release

1.20.3, January 2023

3.3 July 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GPL V3.0

commercial

restricted free version is available

commercial

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.

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++

the server part. Clients available in other languages

C++

Server operating systems

Linux
OS X
Windows

Linux

Linux
Windows

hosted

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC

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

CLI Client
JDBC
ODBC

Supported programming languages

C++

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

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

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes, but depending on the SQL-Server Edition

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

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

User concepts

Access control

Depending on the underlying data source

rights management via user accounts

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.