DBMS > Microsoft Access vs. Snowflake vs. Teradata Aster vs. XTDB

System Properties Comparison Microsoft Access vs. Snowflake vs. Teradata Aster vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

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

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

Platform for big data analytics on multistructured data sources and types

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Document store

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

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

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

www.snowflake.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

www.xtdb.com/docs

Developer

Microsoft

Snowflake Computing Inc.

Teradata

Juxt Ltd.

Initial release

1992

2014

2005

2019

Current release

1902 (16.0.11328.20222), March 2019

1.19, September 2021

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

Open Source

MIT License

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

Clojure

Server operating systems

Windows

Not a real database server, but making use of DLLs

hosted

Linux

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

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

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC
OLE DB

HTTP REST
JDBC

Supported programming languages

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

JavaScript (Node.js)
Python

C
C#
C++
Java
Python
R

Clojure
Java

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

user defined functions

R packages

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

yes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

User concepts

Access control

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

Users with fine-grained authorization concept, user roles and pluggable authentication

fine grained access rights according to SQL-standard

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.