DBMS > Microsoft Access vs. Microsoft SQL Server vs. mSQL vs. SAP HANA

System Properties Comparison Microsoft Access vs. Microsoft SQL Server vs. mSQL vs. SAP HANA

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

Microsofts flagship relational DBMS

mSQL (Mini SQL) is a simple and lightweight RDBMS

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	1.67
Rank	#151	Overall
	#70	Relational DBMS

Score	45.84
Rank	#22	Overall
	#16	Relational DBMS

Website

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

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

hughestech.com.au/products/msql

www.sap.com/products/hana.html

Technical documentation

developer.microsoft.com/en-us/access

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

help.sap.com/hana

Developer

Microsoft

Hughes Technologies

SAP

Initial release

1992

1989

1994

2010

Current release

1902 (16.0.11328.20222), March 2019

SQL Server 2022, November 2022

4.4, October 2021

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

restricted free version is available

commercial

free licenses can be provided

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based 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
Windows

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

Appliance or cloud-service

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

yes

A subset of ANSI SQL is implemented

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

yes

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

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

JDBC
ODBC

Supported programming languages

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

C
C++
Delphi
Java
Perl
PHP
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

SQLScript, R

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

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, but depending on the SQL-Server Edition

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

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

Concurrency

Support for concurrent manipulation of data

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

fine grained access rights according to SQL-standard

yes

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.