DBMS > Faircom DB vs. Geode vs. Microsoft Access vs. Microsoft SQL Server vs. Oracle NoSQL

System Properties Comparison Faircom DB vs. Geode vs. Microsoft Access vs. Microsoft SQL Server vs. Oracle NoSQL

Editorial information provided by DB-Engines

Name

Description

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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

Microsofts flagship relational DBMS

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Primary database model

Key-value store
Relational DBMS

Key-value store

Relational DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.29
Rank	#304	Overall
	#43	Key-value stores
	#136	Relational DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Website

www.faircom.com/products/faircom-db

geode.apache.org

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

www.microsoft.com/en-us/sql-server

www.oracle.com/database/nosql/technologies/nosql

Technical documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

geode.apache.org/docs

developer.microsoft.com/en-us/access

learn.microsoft.com/en-US/sql/sql-server

docs.oracle.com/en/database/other-databases/nosql-database/index.html

Developer

FairCom Corporation

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Microsoft

Oracle

Initial release

1979

2002

1992

1989

2011

Current release

V12, November 2020

1.1, February 2017

1902 (16.0.11328.20222), March 2019

SQL Server 2022, November 2022

23.3, December 2023

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Bundled with Microsoft Office

commercial

restricted free version is available

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

ANSI C, C++

Java

C++

Java

Server operating systems

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

All OS with a Java VM

the JDK (8 or later) is also required

Windows

Not a real database server, but making use of DLLs

Linux
Windows

Linux
Solaris SPARC/x86

Data scheme

schema free, schema optional, schema required, partial schema,

schema-free

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

yes

optional

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, ANSI SQL with proprietary extensions

SQL-like query language (OQL)

yes

but not compliant to any SQL standard

yes

SQL-like DML and DDL statements

APIs and other access methods

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

RESTful HTTP API

Supported programming languages

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

.Net
All JVM based languages
C++
Groovy
Java
Scala

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

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

C
C#
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

user defined functions

yes

since Access 2010 using the ACE-engine

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Cache Event Listeners

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

none

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

Multi-source replication

none

yes, but depending on the SQL-Server Edition

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Eventual Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

yes, on a single node

ACID

but no files for transaction logging

ACID

configurable

ACID within a storage node (=shard)

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Yes, tunable from durable to delayed durability to in-memory

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

off heap cache

User concepts

Access control

Fine grained access rights according to SQL-standard with additional protections for files

Access rights per client and object definable

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

fine grained access rights according to SQL-standard

Access rights for users and roles

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.