DBMS > Interbase vs. Microsoft Access vs. Microsoft Azure AI Search vs. RocksDB vs. Warp 10

System Properties Comparison Interbase vs. Microsoft Access vs. Microsoft Azure AI Search vs. RocksDB vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

Light-weight proven RDBMS

originally from Borland

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

Search-as-a-service for web and mobile app development

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Secondary database models

Vector DBMS

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

Score	4.61
Rank	#72	Overall
	#39	Relational DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	5.59
Rank	#63	Overall
	#7	Search engines

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

www.embarcadero.com/products/interbase

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

azure.microsoft.com/en-us/services/search

rocksdb.org

www.warp10.io

Technical documentation

docs.embarcadero.com/products/interbase

developer.microsoft.com/en-us/access

learn.microsoft.com/en-us/azure/search

github.com/facebook/rocksdb/wiki

www.warp10.io/content/02_Getting_started

Developer

Embarcadero

Microsoft

Facebook, Inc.

SenX

Initial release

1984

1992

2015

2013

2015

Current release

InterBase 2020, December 2019

1902 (16.0.11328.20222), March 2019

8.11.4, April 2024

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

commercial

Open Source

BSD

Open Source

Apache License 2.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

C++

Java

Server operating systems

Android
iOS
Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

hosted

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

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

Secondary indexes

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

RESTful HTTP API

C++ API
Java API

HTTP API
Jupyter
WebSocket

Supported programming languages

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

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

C#
Java
JavaScript
Python

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

yes

since Access 2010 using the ACE-engine

yes

WarpScript

Triggers

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Interbase Change Views

none

yes

Implicit feature of the cloud service

yes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

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

yes

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

User concepts

Access control

fine grained access rights according to SQL-standard

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

yes

using Azure authentication

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.