DBMS > Amazon Redshift vs. Kinetica vs. Microsoft Access vs. OpenTSDB vs. Snowflake

System Properties Comparison Amazon Redshift vs. Kinetica vs. Microsoft Access vs. OpenTSDB vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Fully vectorized database across both GPUs and CPUs

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

Scalable Time Series DBMS based on HBase

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

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	0.69
Rank	#234	Overall
	#107	Relational DBMS

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	1.73
Rank	#147	Overall
	#12	Time Series DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

aws.amazon.com/redshift

www.kinetica.com

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

opentsdb.net

www.snowflake.com

Technical documentation

docs.aws.amazon.com/redshift

docs.kinetica.com

developer.microsoft.com/en-us/access

opentsdb.net/docs/build/html/index.html

docs.snowflake.net/manuals/index.html

Developer

Amazon (based on PostgreSQL)

Kinetica

Microsoft

currently maintained by Yahoo and other contributors

Snowflake Computing Inc.

Initial release

2012

1992

2011

2014

Current release

7.1, August 2021

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

LGPL

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

C++

Java

Server operating systems

hosted

Linux

Windows

Not a real database server, but making use of DLLs

Linux
Windows

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 for metrics, strings for tags

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

yes

but not compliant to any SQL standard

yes

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

HTTP API
Telnet API

CLI Client
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

C++
Java
JavaScript (Node.js)
Python

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

Erlang
Go
Java
Python
R
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

since Access 2010 using the ACE-engine

user defined functions

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on HBase

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

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

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

based on HBase

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

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

In-memory capabilities

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

yes

GPU vRAM or System RAM

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles on table level

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

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.