DBMS > Interbase vs. Machbase Neo vs. Microsoft Access vs. Microsoft Azure Table Storage vs. Microsoft SQL Server

System Properties Comparison Interbase vs. Machbase Neo vs. Microsoft Access vs. Microsoft Azure Table Storage vs. Microsoft SQL Server

Editorial information provided by DB-Engines

Name

Description

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

A Wide Column Store for rapid development using massive semi-structured datasets

Microsofts flagship relational DBMS

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

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	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

www.embarcadero.com/products/interbase

machbase.com

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

azure.microsoft.com/en-us/services/storage/tables

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

Technical documentation

docs.embarcadero.com/products/interbase

machbase.com/dbms

developer.microsoft.com/en-us/access

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

Developer

Embarcadero

Machbase

Microsoft

Initial release

1984

2013

1992

2012

1989

Current release

InterBase 2020, December 2019

V8.0, August 2023

1902 (16.0.11328.20222), March 2019

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

free test version available

commercial

Bundled with Microsoft Office

commercial

restricted free version is available

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

C++

Server operating systems

Android
iOS
Linux
OS X
Windows

Linux
macOS
Windows

Windows

Not a real database server, but making use of DLLs

hosted

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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.

export as XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

but not compliant to any SQL standard

yes

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

RESTful HTTP API

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

Supported programming languages

.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

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

yes

since Access 2010 using the ACE-engine

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

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Implicit feature of the cloud service

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

Replication methods

Methods for redundantly storing data on multiple nodes

Interbase Change Views

selectable replication factor

none

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes, but depending on the SQL-Server Edition

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

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

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

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

Access rights based on private key authentication or shared access signatures

fine grained access rights according to SQL-standard

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.