DBMS > Infobright vs. Microsoft Access vs. OrigoDB vs. RDF4J

System Properties Comparison Infobright vs. Microsoft Access vs. OrigoDB vs. RDF4J

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

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 fully ACID in-memory object graph database

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

Primary database model

Relational DBMS

Document store
Object oriented DBMS

RDF store

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

Score	1.00
Rank	#193	Overall
	#90	Relational DBMS

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	0.03
Rank	#378	Overall
	#51	Document stores
	#18	Object oriented DBMS

Score	0.71
Rank	#231	Overall
	#9	RDF stores

Website

ignitetech.com/softwarelibrary/infobrightdb

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

origodb.com

rdf4j.org

Technical documentation

developer.microsoft.com/en-us/access

origodb.com/docs

rdf4j.org/documentation

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

Microsoft

Robert Friberg et al

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

Initial release

2005

1992

2009

under the name LiveDB

2004

Current release

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

Bundled with Microsoft Office

Open Source

Eclipse Distribution License (EDL), v1.0.

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Java

Server operating systems

Linux
Windows

Windows

Not a real database server, but making use of DLLs

Linux
Windows

Linux
OS X
Unix
Windows

Data scheme

yes

RDF Schemas

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
DAO
ODBC
OLE DB

.NET Client API
HTTP API
LINQ

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

.Net

Java
PHP
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

yes

Triggers

yes

since Access 2010 using the ACE-engine

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Source-replica replication

none

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

depending on model

Transaction concepts

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

ACID

but no files for transaction logging

ACID

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

Write ahead log

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

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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

Role based authorization

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MS Access drops in DB-Engines Ranking
2 May 2013, Paul Andlinger

Microsoft SQL Server regained rank 2 in the DB-Engines popularity ranking
3 December 2012, Matthias Gelbmann

New DB-Engines Ranking shows the popularity of database management systems
3 October 2012, Matthias Gelbmann, Paul Andlinger

show all

Recent citations in the news

Abusing Microsoft Access "Linked Table" Feature to Perform NTLM Forced Authentication Attacks
9 November 2023, Check Point Research

Hackers Exploit Microsoft Access Feature to Steal Windows User’s NTLM Tokens
11 November 2023, CybersecurityNews

MS access program to increase awareness and independence of those living with MS and disability
10 July 2023, Nebraska Medicine

After installing Navisworks, Office 2016 (32-bit) applications stopped launching
8 October 2023, Autodesk Redshift

ACCDE File (What It Is and How to Open One)
27 July 2023, Lifewire

provided by Google News

Ontotext's GraphDB 8.10 Makes Knowledge Graph Experience Faster and Richer
13 June 2019, Markets Insider

provided by Google News

Share this page