DBMS > Amazon DocumentDB vs. Apache IoTDB vs. Microsoft Access vs. Microsoft SQL Server

System Properties Comparison Amazon DocumentDB vs. Apache IoTDB vs. Microsoft Access vs. Microsoft SQL Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

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

Primary database model

Document store

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.89
Rank	#137	Overall
	#24	Document stores

Score	1.19
Rank	#176	Overall
	#15	Time Series DBMS

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Website

aws.amazon.com/documentdb

iotdb.apache.org

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

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

Technical documentation

aws.amazon.com/documentdb/resources

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

developer.microsoft.com/en-us/access

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

Developer

Apache Software Foundation

Microsoft

Initial release

2019

2018

1992

1989

Current release

1.1.0, April 2023

1902 (16.0.11328.20222), March 2019

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Bundled with Microsoft Office

commercial

restricted free version is available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

Server operating systems

hosted

All OS with a Java VM (>= 1.8)

Windows

Not a real database server, but making use of DLLs

Linux
Windows

Data scheme

schema-free

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

SQL-like query language

yes

but not compliant to any SQL standard

yes

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

JDBC
Native API

ADO.NET
DAO
ODBC
OLE DB

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

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

C
C#
C++
Go
Java
Python
Scala

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

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

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

none

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

none

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Integration with Hadoop and Spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong Consistency with Raft

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

Transaction concepts

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

Atomic single-document operations

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

Access rights for users and roles

yes

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

fine grained access rights according to SQL-standard

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.