DBMS > ITTIA vs. Microsoft Access vs. Microsoft SQL Server vs. MySQL

System Properties Comparison ITTIA vs. Microsoft Access vs. Microsoft SQL Server vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Edge Time Series DBMS with Real-Time Stream Processing

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

Microsofts flagship relational DBMS

Widely used open source RDBMS

Primary database model

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Relational DBMS

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

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

Score	0.36
Rank	#272	Overall
	#22	Time Series DBMS

Score	93.76
Rank	#12	Overall
	#8	Relational DBMS

Score	807.76
Rank	#3	Overall
	#3	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

www.ittia.com

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

www.microsoft.com/en-us/sql-server

www.mysql.com

Technical documentation

developer.microsoft.com/en-us/access

learn.microsoft.com/en-US/sql/sql-server

dev.mysql.com/doc

Developer

ITTIA L.L.C.

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2007

1992

1989

1995

Current release

8.7

1902 (16.0.11328.20222), March 2019

SQL Server 2022, November 2022

9.0.0, July 2024

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

restricted free version is available

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

C and C++

C++

C and C++

Server operating systems

Linux
Windows

Windows

Not a real database server, but making use of DLLs

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

Fixed schema

yes

Typing

predefined data types such as float or date

Float/Blob/Integer/String/Unicode/Date/Time/Timestamp/Interval

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

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
RESTful HTTP API
WebSocket

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C++
JavaScript (Node.js)
Python

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

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

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

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes

proprietary syntax

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

tables can be distributed across several files (horizontal partitioning); sharding through federation

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

ACID

but no files for transaction logging

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

table locks or row locks depending on storage engine

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

Database file passwords

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or 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.