DBMS > EJDB vs. JaguarDB vs. Microsoft SQL Server vs. OpenEdge vs. Sequoiadb

System Properties Comparison EJDB vs. JaguarDB vs. Microsoft SQL Server vs. OpenEdge vs. Sequoiadb

Editorial information provided by DB-Engines

Name

Description

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

Performant, highly scalable DBMS for AI and IoT applications

Microsofts flagship relational DBMS

Application development environment with integrated database management system

NewSQL database with distributed OLTP and SQL

Primary database model

Document store

Key-value store
Vector DBMS

Relational DBMS

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.27
Rank	#297	Overall
	#44	Document stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Website

github.com/Softmotions/ejdb

www.jaguardb.com

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

www.progress.com/openedge

www.sequoiadb.com

Technical documentation

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

www.jaguardb.com/support.html

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

documentation.progress.com/output/ua/OpenEdge_latest

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

Softmotions

DataJaguar, Inc.

Microsoft

Progress Software Corporation

Sequoiadb Ltd.

Initial release

2012

2015

1989

1984

2013

Current release

3.3 July 2023

SQL Server 2022, November 2022

OpenEdge 12.2, March 2020

License

Commercial or Open Source

Open Source

GPLv2

Open Source

GPL V3.0

commercial

restricted free version is available

commercial

Open Source

Server: AGPL; Client: Apache V2

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

the server part. Clients available in other languages

C++

Server operating systems

server-less

Linux

Linux
Windows

AIX
HP-UX
Linux
Solaris
Windows

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

oid, date, timestamp, binary, regex

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

Secondary indexes

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

close to SQL 92

SQL-like query language

APIs and other access methods

in-process shared library

JDBC
ODBC

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

JDBC
ODBC

proprietary protocol using JSON

Supported programming languages

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

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

Progress proprietary ABL (Advanced Business Language)

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

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

yes

JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

horizontal partitioning

since Version 11.4

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source 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

Eventual Consistency

Immediate Consistency

Eventual 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

Document is locked during a transaction

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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

rights management via user accounts

fine grained access rights according to SQL-standard

Users and groups

simple password-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.