DBMS > Interbase vs. Microsoft Access vs. Solr vs. SQLite

System Properties Comparison Interbase vs. Microsoft Access vs. Solr vs. SQLite

Please select another system to include it in the comparison.

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

A widely used distributed, scalable search engine based on Apache Lucene

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Search engine

Relational DBMS

Secondary database models

Spatial 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	42.91
Rank	#24	Overall
	#3	Search engines

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.embarcadero.com/products/interbase

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

solr.apache.org

www.sqlite.org

Technical documentation

docs.embarcadero.com/products/interbase

developer.microsoft.com/en-us/access

solr.apache.org/resources.html

www.sqlite.org/docs.html

Developer

Embarcadero

Microsoft

Apache Software Foundation

Dwayne Richard Hipp

Initial release

1984

1992

2006

2000

Current release

InterBase 2020, December 2019

1902 (16.0.11328.20222), March 2019

9.5.0, February 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

Apache Version 2

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

C++

Java

Server operating systems

Android
iOS
Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

server-less

Data scheme

yes

Dynamic Fields enables on-the-fly addition of new fields

yes

dynamic column types

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

yes

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

Solr Parallel SQL Interface

yes

SQL-92 is not fully supported

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
DAO
ODBC
OLE DB

Java API
RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

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

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

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

Interbase procedure and trigger language

yes

since Access 2010 using the ACE-engine

Java plugins

Triggers

yes

since Access 2010 using the ACE-engine

yes

User configurable commands triggered on index changes

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Interbase Change Views

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual 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

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

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

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.