DBMS > Coveo vs. Graph Engine vs. Manticore Search vs. Microsoft SQL Server

System Properties Comparison Coveo vs. Graph Engine 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

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Microsofts flagship relational DBMS

Primary database model

Search engine

Graph DBMS
Key-value store

Search engine

Relational DBMS

Secondary database models

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

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

www.coveo.com

www.graphengine.io

manticoresearch.com

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

Technical documentation

docs.coveo.com

www.graphengine.io/docs/manual

manual.manticoresearch.com

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

Developer

Coveo

Microsoft

Manticore Software

Microsoft

Initial release

2012

2010

2017

1989

Current release

6.0, February 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

MIT License

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.

Implementation language

.NET and C

C++

Server operating systems

hosted

.NET

FreeBSD
Linux
macOS
Windows

Linux
Windows

Data scheme

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

yes

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 query language

yes

APIs and other access methods

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

C#
Java
JavaScript
Python

C#
C++
F#
Visual Basic

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

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

horizontal partitioning

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

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

Consistency concepts

Methods to ensure consistency in a distributed system

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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

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.