DBMS > Coveo vs. Microsoft Access vs. SAP HANA vs. Sphinx

System Properties Comparison Coveo vs. Microsoft Access vs. SAP HANA vs. Sphinx

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

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

In-memory, column based data store. Available as appliance or cloud service

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Search engine

Relational DBMS

Search engine

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

www.coveo.com

www.microsoft.com/en-us/microsoft-365/access

www.sap.com/products/hana.html

sphinxsearch.com

Technical documentation

docs.coveo.com

developer.microsoft.com/en-us/access

help.sap.com/hana

sphinxsearch.com/docs

Developer

Coveo

Microsoft

SAP

Sphinx Technologies Inc.

Initial release

2012

1992

2010

2001

Current release

1902 (16.0.11328.20222), March 2019

2.0 SPS07 (April 4, 2023), April 2023

3.5.1, February 2023

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

Open Source

GPL version 2, commercial licence available

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Server operating systems

hosted

Windows

Not a real database server, but making use of DLLs

Appliance or cloud-service

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

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

yes

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.

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

SQL-like query language (SphinxQL)

APIs and other access methods

RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

JDBC
ODBC

Proprietary protocol

Supported programming languages

C#
Java
JavaScript
Python

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

SQLScript, R

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

yes

none

yes

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

none

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

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

The original contents of fields are not stored in the Sphinx index.

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

a simple user-level security was built in till version Access 2003

yes

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.