DBMS > Microsoft Access vs. Microsoft Azure Cosmos DB vs. Microsoft Azure SQL Database vs. Oracle NoSQL vs. Qdrant

System Properties Comparison Microsoft Access vs. Microsoft Azure Cosmos DB vs. Microsoft Azure SQL Database vs. Oracle NoSQL vs. Qdrant

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

Globally distributed, horizontally scalable, multi-model database service

Database as a Service offering with high compatibility to Microsoft SQL Server

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

A high-performance vector database with neural network or semantic-based matching

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Document store
Key-value store
Relational DBMS

Vector DBMS

Secondary database models

Spatial DBMS

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	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Website

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

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/en-us/products/azure-sql/database

www.oracle.com/database/nosql/technologies/nosql

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

developer.microsoft.com/en-us/access

learn.microsoft.com/azure/cosmos-db

docs.microsoft.com/en-us/azure/azure-sql

docs.oracle.com/en/database/other-databases/nosql-database/index.html

qdrant.tech/documentation

Developer

Microsoft

Oracle

Qdrant

Initial release

1992

2014

2010

2011

2021

Current release

1902 (16.0.11328.20222), March 2019

V12

23.3, December 2023

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

Apache Version 2.0

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

C++

Java

Rust

Server operating systems

Windows

Not a real database server, but making use of DLLs

hosted

Linux
Solaris SPARC/x86

Docker
Linux
macOS
Windows

Data scheme

yes

schema-free

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

optional

Numbers, Strings, Geo, Boolean

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

All properties auto-indexed by default

yes

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like query language

yes

SQL-like DML and DDL statements

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

ADO.NET
JDBC
ODBC

RESTful HTTP API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Supported programming languages

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C#
Go
Java
JavaScript (Node.js)
Python

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

JavaScript

Transact SQL

Triggers

yes

since Access 2010 using the ACE-engine

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service

yes, with always 3 replicas available

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

Collection-level replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

configurable

ACID within a storage node (=shard)

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

off heap cache

yes

User concepts

Access control

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

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

Access rights for users and roles

Key-based authentication

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.