DBMS > Microsoft Access vs. PouchDB vs. Sadas Engine vs. SiriDB vs. Snowflake

System Properties Comparison Microsoft Access vs. PouchDB vs. Sadas Engine vs. SiriDB vs. Snowflake

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

JavaScript DBMS with an API inspired by CouchDB

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Open Source Time Series DBMS

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

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

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

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

Technical documentation

developer.microsoft.com/en-us/access

pouchdb.com/guides

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

docs.siridb.com

docs.snowflake.net/manuals/index.html

Developer

Microsoft

Apache Software Foundation

SADAS s.r.l.

Cesbit

Snowflake Computing Inc.

Initial release

1992

2012

2006

2017

2014

Current release

1902 (16.0.11328.20222), March 2019

7.1.1, June 2019

8.0

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

commercial

free trial version available

Open Source

MIT License

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

JavaScript

C++

Server operating systems

Windows

Not a real database server, but making use of DLLs

server-less, requires a JavaScript environment (browser, Node.js)

AIX
Linux
Windows

Linux

hosted

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

yes

Numeric data

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

via views

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

HTTP REST

only for PouchDB Server
JavaScript API

JDBC
ODBC
Proprietary protocol

HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

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

JavaScript

.Net
C
C#
C++
Groovy
Java
PHP
Python

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

View functions in JavaScript

user defined functions

Triggers

yes

since Access 2010 using the ACE-engine

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal partitioning

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

by using IndexedDB, WebSQL or LevelDB as backend

yes

In-memory capabilities

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

yes

managed by 'Learn by Usage'

yes

User concepts

Access control

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

Access rights for users, groups and roles according to SQL-standard

simple rights management via user accounts

Users with fine-grained authorization concept, user roles and pluggable 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.