DBMS > EJDB vs. EXASOL vs. Interbase vs. Microsoft SQL Server

System Properties Comparison EJDB vs. EXASOL vs. Interbase vs. Microsoft SQL Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Light-weight proven RDBMS

originally from Borland

Microsofts flagship relational DBMS

Primary database model

Document store

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.30
Rank	#294	Overall
	#44	Document stores

Score	2.25
Rank	#120	Overall
	#57	Relational DBMS

Score	5.04
Rank	#71	Overall
	#39	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Website

github.com/Softmotions/ejdb

www.exasol.com

www.embarcadero.com/products/interbase

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

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

www.exasol.com/resources

docs.embarcadero.com/products/interbase

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

Developer

Softmotions

Exasol

Embarcadero

Microsoft

Initial release

2012

2000

1984

1989

Current release

InterBase 2020, December 2019

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

GPLv2

commercial

restricted free version is available

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

Server operating systems

server-less

Android
iOS
Linux
OS X
Windows

Linux
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

APIs and other access methods

in-process shared library

.Net
JDBC
ODBC
WebSocket

ADO.NET
JDBC
ODBC

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

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

Java
Lua
Python
R

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

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

Server-side scripts

Stored procedures

user defined functions

yes

Interbase procedure and trigger language

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

Interbase Change Views

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Multiversion concurreny control

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

Access rights for users, groups and roles according to SQL-standard

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.