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

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

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

A high-performance vector database with neural network or semantic-based matching

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

Primary database model

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

Score	0.22
Rank	#302	Overall
	#24	Graph DBMS
	#13	RDF stores

Score	93.76
Rank	#12	Overall
	#8	Relational DBMS

Score	1.53
Rank	#145	Overall
	#7	Vector DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

cambridgesemantics.com/anzograph

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

github.com/qdrant/qdrant
qdrant.tech

www.snowflake.com

Technical documentation

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

developer.microsoft.com/en-us/access

qdrant.tech/documentation

docs.snowflake.net/manuals/index.html

Developer

Cambridge Semantics

Microsoft

Qdrant

Snowflake Computing Inc.

Initial release

2018

1992

2021

2014

Current release

2.3, January 2021

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

free trial version available

commercial

Bundled with Microsoft Office

Open Source

Apache Version 2.0

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

Rust

Server operating systems

Linux

Windows

Not a real database server, but making use of DLLs

Docker
Linux
macOS
Windows

hosted

Data scheme

Schema-free and OWL/RDFS-schema support

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

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

yes

but not compliant to any SQL standard

yes

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

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

CLI Client
JDBC
ODBC

Supported programming languages

C++
Java
Python

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

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions and aggregates

yes

since Access 2010 using the ACE-engine

user defined functions

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

Automatic sharding

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

none

Collection-level replication

yes

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

Eventual Consistency, tunable consistency

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

Key-based authentication

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.