DBMS > Microsoft Access vs. mSQL vs. MySQL vs. Splunk

System Properties Comparison Microsoft Access vs. mSQL vs. MySQL vs. Splunk

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

mSQL (Mini SQL) is a simple and lightweight RDBMS

Widely used open source RDBMS

Analytics Platform for Big Data

Primary database model

Relational DBMS

Key/Value like access via memcached API

Search engine

Secondary database models

Document store
Spatial DBMS

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

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

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

hughestech.com.au/products/msql

www.mysql.com

www.splunk.com

Technical documentation

developer.microsoft.com/en-us/access

dev.mysql.com/doc

docs.splunk.com/Documentation/Splunk

Developer

Microsoft

Hughes Technologies

Oracle

since 2010, originally MySQL AB, then Sun

Splunk Inc.

Initial release

1992

1994

1995

2003

Current release

1902 (16.0.11328.20222), March 2019

4.4, October 2021

8.4.0, April 2024

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

free licenses can be provided

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Limited free edition and free developer edition available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

C and C++

Server operating systems

Windows

Not a real database server, but making use of DLLs

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Data scheme

yes

Typing

predefined data types such as float or date

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

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

with proprietary extensions

Splunk Search Processing Language for search commands

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

Supported programming languages

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

C
C++
Delphi
Java
Perl
PHP
Tcl

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

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

yes

proprietary syntax

yes

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

but no files for transaction logging

ACID

not for MyISAM storage engine

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

Access rights for users and roles

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.