DBMS > Microsoft Access vs. OrigoDB vs. SQLite vs. Warp 10

System Properties Comparison Microsoft Access vs. OrigoDB vs. SQLite vs. Warp 10

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

A fully ACID in-memory object graph database

Widely used embeddable, in-process RDBMS

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Relational DBMS

Time Series DBMS

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

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

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

origodb.com

www.sqlite.org

www.warp10.io

Technical documentation

developer.microsoft.com/en-us/access

origodb.com/docs

www.sqlite.org/docs.html

www.warp10.io/content/02_Getting_started

Developer

Microsoft

Robert Friberg et al

Dwayne Richard Hipp

SenX

Initial release

1992

2009

under the name LiveDB

2000

2015

Current release

1902 (16.0.11328.20222), March 2019

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

Public Domain

Open Source

Apache License 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Java

Server operating systems

Windows

Not a real database server, but making use of DLLs

Linux
Windows

server-less

Linux
OS X
Windows

Data scheme

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

yes

not rigid because of 'dynamic typing' concept.

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 be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

SQL-92 is not fully supported

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

.NET Client API
HTTP API
LINQ

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP API
Jupyter
WebSocket

Supported programming languages

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

.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

yes

WarpScript

Triggers

yes

since Access 2010 using the ACE-engine

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

client side managed; servers are not synchronized

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

none

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

depending on model

yes

Transaction concepts

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

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

Write ahead log

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

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

Role based authorization

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.