DBMS > Apache Impala vs. Coveo vs. Manticore Search vs. Microsoft SQL Server

System Properties Comparison Apache Impala vs. Coveo vs. Manticore Search vs. Microsoft SQL Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

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

Multi-storage database for search, including full-text search.

Microsofts flagship relational DBMS

Primary database model

Relational DBMS

Search engine

Relational DBMS

Secondary database models

Document store

Time Series DBMS

using the Manticore Columnar Library

Document store
Graph DBMS
Spatial DBMS

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

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Website

impala.apache.org

www.coveo.com

manticoresearch.com

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

Technical documentation

impala.apache.org/impala-docs.html

docs.coveo.com

manual.manticoresearch.com

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

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Coveo

Manticore Software

Microsoft

Initial release

2013

2012

2017

1989

Current release

4.1.0, June 2022

6.0, February 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

GPL version 2

commercial

restricted free version is 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.

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

Server operating systems

Linux

hosted

FreeBSD
Linux
macOS
Windows

Linux
Windows

Data scheme

yes

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

Fixed schema

yes

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

yes

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

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

Supported programming languages

All languages supporting JDBC/ODBC

C#
Java
JavaScript
Python

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

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

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

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

Sharding

Partitioning is done manually, search queries against distributed index is supported

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

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

Synchronous replication based on Galera library

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

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 Manticore index.

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

granular access controls, API key management, content filters

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.