DBMS > Amazon Redshift vs. Microsoft Access vs. NCache vs. Valentina Server

System Properties Comparison Amazon Redshift vs. Microsoft Access vs. NCache vs. Valentina Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

Open-Source and Enterprise in-memory Key-Value Store

Object-relational database and reports server

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Secondary database models

Document store
Search engine

Using distributed Lucene

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	0.94
Rank	#195	Overall
	#29	Key-value stores

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

aws.amazon.com/redshift

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

www.alachisoft.com/ncache

www.valentina-db.net

Technical documentation

docs.aws.amazon.com/redshift

developer.microsoft.com/en-us/access

www.alachisoft.com/resources/docs

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Amazon (based on PostgreSQL)

Microsoft

Alachisoft

Paradigma Software

Initial release

2012

1992

2005

1999

Current release

1902 (16.0.11328.20222), March 2019

5.3.3, April 2024

5.7.5

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

Enterprise Edition available

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#, .NET, .NET Core, Java

Server operating systems

hosted

Windows

Not a real database server, but making use of DLLs

Linux
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

partial

Supported data types are Lists, Queues, Hashsets, Dictionary and Counter

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

but not compliant to any SQL standard

SQL-like query syntax and LINQ for searching the cache. Cache Synchronization with SQL Server using SQL dependency.

yes

APIs and other access methods

JDBC
ODBC

ADO.NET
DAO
ODBC
OLE DB

IDistributedCache
JCache
LINQ
Proprietary native API

ODBC

Supported programming languages

All languages supporting JDBC/ODBC

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

.Net
.Net Core
C#
Java
JavaScript (Node.js)
Python
Scala

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

user defined functions

in Python

yes

since Access 2010 using the ACE-engine

support for stored procedures with SQL-Server CLR

yes

Triggers

yes

since Access 2010 using the ACE-engine

yes

Notifications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes, with selectable consistency level

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency
Strong Eventual Consistency over WAN with Conflict Resolution using Bridge Topology

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

optimistic locking and pessimistic locking

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

User concepts

Access control

fine grained access rights according to SQL-standard

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

Authentication to access the cache via Active Directory/LDAP (possible roles: user, administrator)

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

NCache has been the market leader in .NET Distributed Caching since 2005 . NCache...
» more

Competitive advantages

NCache is 100% .NET/ .NET Core based which fully supports ASP.NET Core Sessions ,...
» more

Typical application scenarios

NCache enables industries like retail, finance, banking IoT, travel, ecommerce, healthcare...
» more

Key customers

Bank of America, Citi, Natures Way, Charter Spectrum, Barclays, Henry Schein, GBM,...
» more

Market metrics

Market Leader in .NET Distributed Caching since 2005.
» more

Licensing and pricing models

NCache Open Source is free on an as-is basis without any support. NCache Enterprise...
» more

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.