DBMS > Faircom DB vs. FileMaker vs. Ingres vs. MariaDB vs. Microsoft Access

System Properties Comparison Faircom DB vs. FileMaker vs. Ingres vs. MariaDB vs. Microsoft Access

Editorial information provided by DB-Engines

Name

Description

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

FileMaker is a cross-platform RDBMS that includes a GUI frontend.

Well established RDBMS

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

Primary database model

Key-value store
Relational DBMS

Relational 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	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	48.20
Rank	#20	Overall
	#14	Relational DBMS

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	93.21
Rank	#13	Overall
	#9	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Website

www.faircom.com/products/faircom-db

www.claris.com/filemaker

www.actian.com/databases/ingres

mariadb.com

Site of MariaDB Corporation
mariadb.org

Site of MariaDB Foundation

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

Technical documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

www.claris.com/resources/documentation

docs.actian.com/ingres

mariadb.com/kb/en/library

developer.microsoft.com/en-us/access

Developer

FairCom Corporation

Claris

a subsidiary of Apple

Actian Corporation

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

The lead developer Monty Widenius is the original author of MySQL

Microsoft

Initial release

1979

1983

1974

originally developed at University Berkely in early 1970s

2009

Fork of MySQL, which was first released in 1995

1992

Current release

V12, November 2020

19.4.1, November 2021

11.2, May 2022

11.3.2, February 2024

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

Open Source

GPL version 2, commercial enterprise subscription available

commercial

Bundled with Microsoft Office

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

ANSI C, C++

C and C++

C++

Server operating systems

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

iOS

client part only
Linux
OS X
Windows

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

FreeBSD
Linux
Solaris
Windows

ColumnStore storage engine not available on Windows

Windows

Not a real database server, but making use of DLLs

Data scheme

schema free, schema optional, schema required, partial schema,

yes

Dynamic columns are supported

yes

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

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

A http query request can return the data in XML format

but tools for importing/exporting data from/to XML-files available

yes

Secondary indexes

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

yes

via plugins

yes

with proprietary extensions

yes

but not compliant to any SQL standard

APIs and other access methods

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

Filemaker WebDirect
JDBC
ODBC

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
DAO
ODBC
OLE DB

Supported programming languages

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

PHP

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

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

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

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

none

horizontal partitioning

Ingres Star to access multiple databases simultaneously

several options for horizontal partitioning and Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

Source-replica replication, warm standby

since Version 14

Ingres Replicator

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

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

tunable from ACID to Eventually Consistent

ACID

not for MyISAM storage engine

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

Durability

Support for making data persistent

Yes, tunable from durable to delayed durability to in-memory

yes

not for in-memory storage engine

yes

but no files for transaction logging

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 with additional protections for files

simple rights management via user accounts and connection to external directory services

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

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.