DBMS > Coveo vs. IBM Db2 Event Store vs. Microsoft Access vs. SQLite

System Properties Comparison Coveo vs. IBM Db2 Event Store vs. Microsoft Access vs. SQLite

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

Distributed Event Store optimized for Internet of Things use cases

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.)

Widely used embeddable, in-process RDBMS

Primary database model

Search engine

Event Store
Time Series DBMS

Relational DBMS

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

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	0.19
Rank	#323	Overall
	#2	Event Stores
	#28	Time Series DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.coveo.com

www.ibm.com/products/db2-event-store

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

www.sqlite.org

Technical documentation

docs.coveo.com

www.ibm.com/docs/en/db2-event-store

developer.microsoft.com/en-us/access

www.sqlite.org/docs.html

Developer

Coveo

IBM

Microsoft

Dwayne Richard Hipp

Initial release

2012

2017

1992

2000

Current release

2.0

1902 (16.0.11328.20222), March 2019

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

free developer edition available

commercial

Bundled with Microsoft Office

Open Source

Public Domain

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

C and C++

C++

Server operating systems

hosted

Linux

Linux, macOS, Windows for the developer addition

Windows

Not a real database server, but making use of DLLs

server-less

Data scheme

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

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL

Support of SQL

yes

through the embedded Spark runtime

yes

but not compliant to any SQL standard

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
Java
JavaScript
Python

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

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Active-active shard replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual 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

No - written data is immutable

yes

via file-system locks

Durability

Support for making data persistent

yes

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

yes

but no files for transaction logging

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

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

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.