DBMS > Microsoft Access vs. RRDtool vs. SiteWhere vs. Snowflake

System Properties Comparison Microsoft Access vs. RRDtool vs. SiteWhere vs. Snowflake

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

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

M2M integration platform for persisting/querying time series data

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

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

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

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

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

oss.oetiker.ch/rrdtool

github.com/sitewhere/sitewhere

www.snowflake.com

Technical documentation

developer.microsoft.com/en-us/access

oss.oetiker.ch/rrdtool/doc

sitewhere1.sitewhere.io/index.html

docs.snowflake.net/manuals/index.html

Developer

Microsoft

Tobias Oetiker

SiteWhere

Snowflake Computing Inc.

Initial release

1992

1999

2010

2014

Current release

1902 (16.0.11328.20222), March 2019

1.8.0, 2022

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

GPL V2 and FLOSS

Open Source

Common Public Attribution License Version 1.0

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

Implementations in Java (e.g. RRD4J) and C# available

Java

Server operating systems

Windows

Not a real database server, but making use of DLLs

HP-UX
Linux

Linux
OS X
Windows

hosted

Data scheme

yes

predefined scheme

yes

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

Typing

predefined data types such as float or date

yes

Numeric data only

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.

Exporting into and restoring from XML files possible

yes

Secondary indexes

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

in-process shared library
Pipes

HTTP REST

CLI Client
JDBC
ODBC

Supported programming languages

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

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

user defined functions

Triggers

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on HBase

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

based on HBase

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

by using the rrdcached daemon

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

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

Users with fine-grained authorization concept

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.