DBMS > AgensGraph vs. GeoSpock vs. Microsoft Access vs. Postgres-XL vs. Snowflake

System Properties Comparison AgensGraph vs. GeoSpock vs. Microsoft Access vs. Postgres-XL vs. Snowflake

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Spatial and temporal data processing engine for extreme data scale

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

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

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

Primary database model

Graph DBMS
Relational DBMS

Relational DBMS

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

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

Score	0.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

bitnine.net/agensgraph

geospock.com

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

www.postgres-xl.org

www.snowflake.com

Technical documentation

bitnine.net/documentation

developer.microsoft.com/en-us/access

www.postgres-xl.org/documentation

docs.snowflake.net/manuals/index.html

Developer

Bitnine Global Inc.

GeoSpock

Microsoft

Snowflake Computing Inc.

Initial release

2016

1992

2014

since 2012, originally named StormDB

2014

Current release

2.1, December 2018

2.0, September 2019

1902 (16.0.11328.20222), March 2019

10 R1, October 2018

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Bundled with Microsoft Office

Open Source

Mozilla public license

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

Java, Javascript

C++

Server operating systems

Linux
OS X
Windows

hosted

Windows

Not a real database server, but making use of DLLs

Linux
macOS

hosted

Data scheme

depending on used data model

yes

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

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

XML type, but no XML query functionality

yes

Secondary indexes

yes

temporal, categorical

yes

SQL

Support of SQL

yes

ANSI SQL for query only (using Presto)

yes

but not compliant to any SQL standard

yes

distributed, parallel query execution

yes

APIs and other access methods

Cypher Query Language
JDBC

JDBC

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

CLI Client
JDBC
ODBC

Supported programming languages

C
Java
JavaScript
Python

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

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

user defined functions

Triggers

yes

since Access 2010 using the ACE-engine

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Automatic sharding

none

horizontal partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

MVCC

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.

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per table

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

fine grained access rights according to SQL-standard

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.