DBMS > Firebird vs. Microsoft SQL Server vs. Oracle Berkeley DB vs. TempoIQ

System Properties Comparison Firebird vs. Microsoft SQL Server vs. Oracle Berkeley DB vs. TempoIQ

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

Description

Firebird is an open source RDBMS forked from Borland's InterBase

Microsofts flagship relational DBMS

Widely used in-process key-value store

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	21.06
Rank	#31	Overall
	#19	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	2.52
Rank	#114	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Website

www.firebirdsql.org

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

www.oracle.com/database/technologies/related/berkeleydb.html

tempoiq.com (offline)

Technical documentation

www.firebirdsql.org/en/reference-manuals

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

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Firebird Foundation

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

TempoIQ

Initial release

2000

As fork of Borland's InterBase

1989

1994

2012

Current release

5.0.0, January 2024

SQL Server 2022, November 2022

18.1.40, May 2020

License

Commercial or Open Source

Open Source

Initial Developer's Public License

commercial

restricted free version is available

Open Source

commercial license available

commercial

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 and C++

C++

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

AIX
FreeBSD
HP-UX
Linux
OS X
server-less

Firebird Embedded Server
Solaris
Unix
Windows

Linux
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
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.

yes

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

APIs and other access methods

ADO.NET
C/C++ API
JDBC

Jaybird
ODBC
OLE DB

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

HTTP API

Supported programming languages

C
C#
C++
Delphi
Java
JavaScript

Node.js
Lua
Perl
PHP
Python
Ruby

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

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

PSQL

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

Triggers

yes

only for the SQL API

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

none

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes, but depending on the SQL-Server Edition

Source-replica replication

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

Concurrency

Support for concurrent manipulation of data

yes

Features a multi-generational MVCC architecture, readers do not block writers

yes

Durability

Support for making data persistent

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

Users with fine-grained authorization concept

fine grained access rights according to SQL-standard

simple authentication-based access control

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.