DBMS > Microsoft Access vs. Microsoft Azure Cosmos DB vs. OpenQM vs. Pinecone

System Properties Comparison Microsoft Access vs. Microsoft Azure Cosmos DB vs. OpenQM vs. Pinecone

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

Globally distributed, horizontally scalable, multi-model database service

QpenQM is a high-performance, self-tuning, multi-value DBMS

A managed, cloud-native vector database

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Multivalue DBMS

Vector DBMS

Secondary database models

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	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	3.16
Rank	#95	Overall
	#2	Vector DBMS

Website

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

azure.microsoft.com/services/cosmos-db

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.pinecone.io

Technical documentation

developer.microsoft.com/en-us/access

learn.microsoft.com/azure/cosmos-db

docs.pinecone.io/docs/overview

Developer

Microsoft

Rocket Software, originally Martin Phillips

Pinecone Systems, Inc

Initial release

1992

2014

1993

2019

Current release

1902 (16.0.11328.20222), March 2019

3.4-12

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

Open Source

GPLv2, extended commercial license available

commercial

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++

Server operating systems

Windows

Not a real database server, but making use of DLLs

hosted

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

hosted

Data scheme

yes

schema-free

yes

with some exceptions

Typing

predefined data types such as float or date

yes

JSON types

String, Number, 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

SQL

Support of SQL

yes

but not compliant to any SQL standard

SQL-like query language

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

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

RESTful HTTP API

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
Basic
C
Java
Objective C
PHP
Python

Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

JavaScript

yes

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

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

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

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

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.

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

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.