DBMS > Atos Standard Common Repository vs. Google BigQuery vs. Memgraph vs. Microsoft Access

System Properties Comparison Atos Standard Common Repository vs. Google BigQuery vs. Memgraph vs. Microsoft Access

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Large scale data warehouse service with append-only tables

An open source graph database built for real-time streaming and compatible with Neo4j

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

Primary database model

Document store
Key-value store

Relational DBMS

Graph DBMS

Relational DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	3.02
Rank	#98	Overall
	#8	Graph DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

cloud.google.com/bigquery

memgraph.com

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

Technical documentation

cloud.google.com/bigquery/docs

memgraph.com/docs

developer.microsoft.com/en-us/access

Social network pages

Developer

Atos Convergence Creators

Google

Memgraph Ltd

Microsoft

Initial release

2016

2010

2017

1992

Current release

1703

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Open Source

BSL 1.1; commercial license for enterprise edition available

commercial

Bundled with Microsoft Office

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

C and C++

C++

Server operating systems

Linux

hosted

Linux

Windows

Not a real database server, but making use of DLLs

Data scheme

Schema and schema-less with LDAP views

yes

schema-free and schema-optional

yes

Typing

predefined data types such as float or date

optional

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

SQL

Support of SQL

yes

but not compliant to any SQL standard

APIs and other access methods

LDAP

RESTful HTTP/JSON API

Bolt protocol
Cypher query language

ADO.NET
DAO
ODBC
OLE DB

Supported programming languages

All languages with LDAP bindings

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
C
C++
Elixir
Go
Haskell
Java
JavaScript
PHP
Python
Ruby
Scala

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

since Access 2010 using the ACE-engine

Triggers

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

dynamic graph partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using RAFT

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

relationships in graphs

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Atomic execution of specific operations

Since BigQuery is designed for querying data

ACID

with snapshot isolation

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

with periodic snapshot and write-ahead logging (WAL) of changes

yes

but no files for transaction logging

In-memory capabilities

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

yes

User concepts

Access control

LDAP bind authentication

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Users, roles and permissions

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

More information provided by the system vendor

Specific characteristics

Memgraph directly connects to your streaming infrastructure so you and your team...
» more

Competitive advantages

Business Source License ensures a future for the Memgraph community MAGE algorithm...
» more

Typical application scenarios

Graph algorithms in bioinformatics Social network analysis Cryptocurrency network...
» more

Licensing and pricing models

You can check out our pricing model and licenses on the company website .
» 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.