DBMS > Apache Drill vs. CouchDB vs. Microsoft SQL Server vs. PouchDB

System Properties Comparison Apache Drill vs. CouchDB vs. Microsoft SQL Server vs. PouchDB

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

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Microsofts flagship relational DBMS

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Document store
Relational DBMS

Document store

Relational DBMS

Document store

Secondary database models

Spatial DBMS

using the Geocouch extension

Document store
Graph 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	9.30
Rank	#45	Overall
	#7	Document stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Website

drill.apache.org

couchdb.apache.org

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

pouchdb.com

Technical documentation

drill.apache.org/docs

docs.couchdb.org/en/stable

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

pouchdb.com/guides

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Microsoft

Apache Software Foundation

Initial release

2012

2005

1989

2012

Current release

1.20.3, January 2023

3.3.3, December 2023

SQL Server 2022, November 2022

7.1.1, June 2019

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache version 2

commercial

restricted free version is available

Open Source

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

Erlang

C++

JavaScript

Server operating systems

Linux
OS X
Windows

Android
BSD
Linux
OS X
Solaris
Windows

Linux
Windows

server-less, requires a JavaScript environment (browser, Node.js)

Data scheme

schema-free

yes

schema-free

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

via views

yes

via views

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

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

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

C++

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

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

JavaScript

Server-side scripts

Stored procedures

user defined functions

View functions in JavaScript

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

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

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

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes, but depending on the SQL-Server Edition

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

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

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

Access rights for users can be defined per database

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.