DBMS > MariaDB vs. Microsoft Access vs. ToroDB vs. Yanza

System Properties Comparison MariaDB vs. Microsoft Access vs. ToroDB vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

MySQL application compatible open source RDBMS, enhanced with high availability, security, interoperability and performance capabilities. MariaDB ColumnStore provides a column-oriented storage engine and MariaDB Xpand supports distributed SQL.

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 MongoDB-compatible JSON document store, built on top of PostgreSQL

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Document store

Time Series DBMS

Secondary database models

Document store
Graph DBMS

with OQGraph storage engine
Spatial DBMS

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

Score	93.21
Rank	#13	Overall
	#9	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Website

mariadb.com

Site of MariaDB Corporation
mariadb.org

Site of MariaDB Foundation

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

github.com/torodb/server

yanza.com

Technical documentation

mariadb.com/kb/en/library

developer.microsoft.com/en-us/access

Developer

MariaDB Corporation Ab (MariaDB Enterprise),
MariaDB Foundation (community MariaDB Server)

The lead developer Monty Widenius is the original author of MySQL

Microsoft

8Kdata

Yanza

Initial release

2009

Fork of MySQL, which was first released in 1995

1992

2016

2015

Current release

11.3.2, February 2024

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

GPL version 2, commercial enterprise subscription available

commercial

Bundled with Microsoft Office

Open Source

AGPL-V3

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C and C++

C++

Java

Server operating systems

FreeBSD
Linux
Solaris
Windows

ColumnStore storage engine not available on Windows

Windows

Not a real database server, but making use of DLLs

All OS with a Java 7 VM

Windows

Data scheme

yes

Dynamic columns are supported

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

but not compliant to any SQL standard

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
DAO
ODBC
OLE DB

HTTP API

Supported programming languages

Ada
C
C#
C++
D
Eiffel
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

PL/SQL compatibility added with version 10.3

yes

since Access 2010 using the ACE-engine

Triggers

yes

since Access 2010 using the ACE-engine

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

several options for horizontal partitioning and Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Source-replica 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
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

not for in-memory storage engine

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

with MEMORY storage engine

User concepts

Access control

fine grained access rights according to SQL-standard

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

Access rights for users and roles

More information provided by the system vendor

Specific characteristics

MariaDB is the most powerful open source relational database – modern SQL and JSON...
» more

Competitive advantages

MariaDB Servers have many features unavailable in other open source relational databases....
» more

Typical application scenarios

Web, SaaS and Cloud operational applications that require high availability, scalability...
» more

Key customers

Deutsche Bank, DBS Bank, Nasdaq, Red Hat, ServiceNow, Verizon and Walgreens Featured...
» more

Market metrics

MariaDB is the default database in the LAMP stack supplied by Red Hat and SUSE Linux,...
» more

Licensing and pricing models

MariaDB plc subscriptions cover our free, open source database, Community Server,...
» more

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.