DBMS > Amazon Redshift vs. KeyDB vs. Microsoft Access vs. Microsoft Azure AI Search vs. Microsoft Azure Synapse Analytics

System Properties Comparison Amazon Redshift vs. KeyDB vs. Microsoft Access vs. Microsoft Azure AI Search vs. Microsoft Azure Synapse Analytics

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

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

Search-as-a-service for web and mobile app development

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

Primary database model

Secondary database models

Vector DBMS

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	0.63
Rank	#232	Overall
	#32	Key-value stores

Score	93.76
Rank	#12	Overall
	#8	Relational DBMS

Score	5.75
Rank	#58	Overall
	#7	Search engines

Score	18.98
Rank	#31	Overall
	#19	Relational DBMS

Website

aws.amazon.com/redshift

github.com/Snapchat/KeyDB
keydb.dev

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

azure.microsoft.com/en-us/services/search

azure.microsoft.com/services/synapse-analytics

Technical documentation

docs.aws.amazon.com/redshift

docs.keydb.dev

developer.microsoft.com/en-us/access

learn.microsoft.com/en-us/azure/search

docs.microsoft.com/azure/synapse-analytics

Developer

Amazon (based on PostgreSQL)

EQ Alpha Technology Ltd.

Microsoft

Initial release

2012

2019

1992

2015

2016

Current release

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Open Source

BSD-3

commercial

Bundled with Microsoft Office

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

hosted

Linux

Windows

Not a real database server, but making use of DLLs

hosted

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

restricted

yes

by using the Redis Search module

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

but not compliant to any SQL standard

yes

APIs and other access methods

JDBC
ODBC

Proprietary protocol

RESP - REdis Serialization Protoco

ADO.NET
DAO
ODBC
OLE DB

RESTful HTTP API

ADO.NET
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

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

C#
Java
JavaScript
Python

C#
Java
PHP

Server-side scripts

Stored procedures

user defined functions

in Python

Lua

yes

since Access 2010 using the ACE-engine

Transact SQL

Triggers

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

none

yes

Implicit feature of the cloud service

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Optimistic locking, atomic execution of commands blocks and scripts

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

fine grained access rights according to SQL-standard

simple password-based access control and ACL

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

yes

using Azure authentication

yes

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.