DBMS > Microsoft Access vs. Microsoft Azure Cosmos DB vs. Quasardb vs. Sqrrl

System Properties Comparison Microsoft Access vs. Microsoft Azure Cosmos DB vs. Quasardb vs. Sqrrl

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

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

Distributed, high-performance timeseries database

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

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

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Website

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

azure.microsoft.com/services/cosmos-db

quasar.ai

sqrrl.com

Technical documentation

developer.microsoft.com/en-us/access

learn.microsoft.com/azure/cosmos-db

doc.quasar.ai/master

Developer

Microsoft

quasardb

Amazon

originally Sqrrl Data, Inc.

Initial release

1992

2014

2009

2012

Current release

1902 (16.0.11328.20222), March 2019

3.14.1, January 2024

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

Java

Server operating systems

Windows

Not a real database server, but making use of DLLs

hosted

BSD
Linux
OS X
Windows

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

integer and binary

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.

Secondary indexes

yes

All properties auto-indexed by default

yes

with tags

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

HTTP API

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

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
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

JavaScript

Triggers

yes

since Access 2010 using the ACE-engine

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

consistent hashing

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service

Source-replica replication with selectable replication factor

selectable replication factor

making use of Hadoop

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

with Hadoop integration

yes

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

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

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

Atomic updates per row, document, or graph entity

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

by using LevelDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Transient mode

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

Cryptographically strong user authentication and audit trail

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.