DBMS > Apache Drill vs. Coveo vs. Microsoft SQL Server vs. Prometheus vs. ToroDB

System Properties Comparison Apache Drill vs. Coveo vs. Microsoft SQL Server vs. Prometheus vs. ToroDB

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

Microsofts flagship relational DBMS

Open-source Time Series DBMS and monitoring system

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Document store
Relational DBMS

Secondary database models

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	2.28
Rank	#114	Overall
	#11	Search engines

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Website

drill.apache.org

www.coveo.com

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

prometheus.io

github.com/torodb/server

Technical documentation

drill.apache.org/docs

docs.coveo.com

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

prometheus.io/docs

Developer

Apache Software Foundation

Coveo

Microsoft

8Kdata

Initial release

2012

1989

2015

2016

Current release

1.20.3, January 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

restricted free version is available

Open Source

Apache 2.0

Open Source

AGPL-V3

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

Java

Server operating systems

Linux
OS X
Windows

hosted

Linux
Windows

All OS with a Java 7 VM

Data scheme

schema-free

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

yes

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

yes

string, integer, double, boolean, date, object_id

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

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP API

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

RESTful HTTP/JSON API

Supported programming languages

C++

C#
Java
JavaScript
Python

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

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

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

yes

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, but depending on the SQL-Server Edition

yes

by Federation

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

none

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

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

granular access controls, API key management, content filters

fine grained access rights according to SQL-standard

Access rights for users and roles

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.