DBMS > AnzoGraph DB vs. Microsoft Access vs. Snowflake vs. Teradata

System Properties Comparison AnzoGraph DB vs. Microsoft Access vs. Snowflake vs. Teradata

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable graph database built for online analytics and data harmonization with MPP scaling, high-performance analytical algorithms and reasoning, and virtualization

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

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Graph DBMS
RDF store

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.29
Rank	#303	Overall
	#25	Graph DBMS
	#14	RDF stores

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Website

cambridgesemantics.com/anzograph

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

www.snowflake.com

www.teradata.com

Technical documentation

docs.cambridgesemantics.com/anzograph/userdoc/home.htm

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

docs.teradata.com

Developer

Cambridge Semantics

Microsoft

Snowflake Computing Inc.

Teradata

Initial release

2018

1992

2014

1984

Current release

2.3, January 2021

1902 (16.0.11328.20222), March 2019

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

commercial

free trial version available

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

Linux

Windows

Not a real database server, but making use of DLLs

hosted

hosted
Linux

Data scheme

Schema-free and OWL/RDFS-schema support

yes

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

yes

Typing

predefined data types such as float or date

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

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

SPARQL and SPARQL* as primary query language. Cypher preview.

yes

but not compliant to any SQL standard

yes

SQL 2016 + extensions

APIs and other access methods

Apache Mule
gRPC
JDBC
Kafka
OData access for BI tools
OpenCypher
RESTful HTTP API
SPARQL

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

C++
Java
Python

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

JavaScript (Node.js)
Python

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

user defined functions and aggregates

yes

since Access 2010 using the ACE-engine

user defined functions

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

yes

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

none

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

Immediate Consistency

Foreign keys

Referential integrity

not needed in graphs

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

User concepts

Access control

Access rights for users and roles

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.