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

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

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

Well established RDBMS

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

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Primary database model

Document store
Key-value store

Relational DBMS

RDF store

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Website

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

cloud.google.com/bigquery

www.actian.com/databases/ingres

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

rdf4j.org

Technical documentation

cloud.google.com/bigquery/docs

docs.actian.com/ingres

developer.microsoft.com/en-us/access

rdf4j.org/documentation

Developer

Atos Convergence Creators

Google

Actian Corporation

Microsoft

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Initial release

2016

2010

1974

originally developed at University Berkely in early 1970s

1992

2004

Current release

1703

11.2, May 2022

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

Eclipse Distribution License (EDL), v1.0.

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

Java

Server operating systems

Linux

hosted

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Windows

Not a real database server, but making use of DLLs

Linux
OS X
Unix
Windows

Data scheme

Schema and schema-less with LDAP views

yes

RDF Schemas

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

but tools for importing/exporting data from/to XML-files available

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

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

ADO.NET
DAO
ODBC
OLE DB

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

All languages with LDAP bindings

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

since Access 2010 using the ACE-engine

yes

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

horizontal partitioning

Ingres Star to access multiple databases simultaneously

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Ingres Replicator

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

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

but no files for transaction logging

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

in-memory storage is supported as well

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)

fine grained access rights according to SQL-standard

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

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.