DBMS > Microsoft Access vs. RavenDB vs. SiriDB vs. SQLite vs. Teradata Aster

System Properties Comparison Microsoft Access vs. RavenDB vs. SiriDB vs. SQLite vs. Teradata Aster

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

Open Source Time Series DBMS

Widely used embeddable, in-process RDBMS

Platform for big data analytics on multistructured data sources and types

Primary database model

Secondary database models

Graph DBMS
Spatial 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	2.84
Rank	#101	Overall
	#18	Document stores

Score	0.07
Rank	#378	Overall
	#42	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

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

ravendb.net

siridb.com

www.sqlite.org

Technical documentation

developer.microsoft.com/en-us/access

ravendb.net/docs

docs.siridb.com

www.sqlite.org/docs.html

Developer

Microsoft

Hibernating Rhinos

Cesbit

Dwayne Richard Hipp

Teradata

Initial release

1992

2010

2017

2000

2005

Current release

1902 (16.0.11328.20222), March 2019

5.4, July 2022

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

AGPL version 3, commercial license available

Open Source

MIT License

Open Source

Public Domain

commercial

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

Server operating systems

Windows

Not a real database server, but making use of DLLs

Linux
macOS
Raspberry Pi
Windows

Linux

server-less

Linux

Data scheme

yes

schema-free

yes

dynamic column types

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

Typing

predefined data types such as float or date

yes

Numeric data

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.

yes

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like query language (RQL)

yes

SQL-92 is not fully supported

yes

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

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

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

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

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

yes

R packages

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

yes

none

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

but no files for transaction logging

ACID, Cluster-wide transaction available

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

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

Authorization levels configured per client per database

simple rights management via user accounts

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.