DBMS > Microsoft Access vs. Microsoft SQL Server vs. Percona Server for MongoDB vs. SiriDB

System Properties Comparison Microsoft Access vs. Microsoft SQL Server vs. Percona Server for MongoDB vs. SiriDB

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

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Open Source Time Series DBMS

Primary database model

Relational DBMS

Document store

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.52
Rank	#254	Overall
	#39	Document stores

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Website

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

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

www.percona.com/mongodb/software/percona-server-for-mongodb

siridb.com

Technical documentation

developer.microsoft.com/en-us/access

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

docs.percona.com/percona-distribution-for-mongodb

docs.siridb.com

Developer

Microsoft

Percona

Cesbit

Initial release

1992

1989

2015

2017

Current release

1902 (16.0.11328.20222), March 2019

SQL Server 2022, November 2022

3.4.10-2.10, November 2017

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

restricted free version is available

Open Source

GPL Version 2

Open Source

MIT License

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

C++

Server operating systems

Windows

Not a real database server, but making use of DLLs

Linux
Windows

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data

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

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

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

proprietary protocol using JSON

HTTP API

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

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

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

JavaScript

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, but depending on the SQL-Server Edition

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
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

via In-Memory Engine

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

Access rights for users and roles

simple rights management via user accounts

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.