DBMS > H2GIS vs. Interbase vs. Machbase Neo vs. Microsoft Access vs. SQLite

System Properties Comparison H2GIS vs. Interbase vs. Machbase Neo vs. Microsoft Access vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Spatial extension of H2

Light-weight proven RDBMS

originally from Borland

TimeSeries DBMS for AIoT and BigData

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

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Relational DBMS

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

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.h2gis.org

www.embarcadero.com/products/interbase

machbase.com

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

www.sqlite.org

Technical documentation

www.h2gis.org/docs/home

docs.embarcadero.com/products/interbase

machbase.com/dbms

developer.microsoft.com/en-us/access

www.sqlite.org/docs.html

Developer

CNRS

Embarcadero

Machbase

Microsoft

Dwayne Richard Hipp

Initial release

2013

1984

2013

1992

2000

Current release

InterBase 2020, December 2019

V8.0, August 2023

1902 (16.0.11328.20222), March 2019

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

LGPL 3.0

commercial

free test version available

commercial

Bundled with Microsoft Office

Open Source

Public Domain

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

Java

C++

Server operating systems

Android
iOS
Linux
OS X
Windows

Linux
macOS
Windows

Windows

Not a real database server, but making use of DLLs

server-less

Data scheme

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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.

export as XML data possible

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

but not compliant to any SQL standard

yes

SQL-92 is not fully supported

APIs and other access methods

ADO.NET
JDBC
ODBC

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

ADO.NET
DAO
ODBC
OLE DB

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

based on H2

yes

Interbase procedure and trigger language

yes

since Access 2010 using the ACE-engine

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on H2

Interbase Change Views

selectable replication factor

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

Transaction concepts

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

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

Multiversion concurreny control

yes

via file-system locks

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.

yes

volatile and lookup table

yes

User concepts

Access control

yes

based on H2

fine grained access rights according to SQL-standard

simple password-based access control

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.