DBMS > EJDB vs. Microsoft SQL Server vs. Netezza vs. OpenEdge vs. RavenDB

System Properties Comparison EJDB vs. Microsoft SQL Server vs. Netezza vs. OpenEdge vs. RavenDB

Editorial information provided by DB-Engines

Name

Description

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

Microsofts flagship relational DBMS

Data warehouse and analytics appliance part of IBM PureSystems

Application development environment with integrated database management system

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Document store

Relational DBMS

Document store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	8.59
Rank	#45	Overall
	#29	Relational DBMS

Score	3.45
Rank	#85	Overall
	#46	Relational DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Website

github.com/Softmotions/ejdb

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

www.ibm.com/products/netezza

www.progress.com/openedge

ravendb.net

Technical documentation

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

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

documentation.progress.com/output/ua/OpenEdge_latest

ravendb.net/docs

Developer

Softmotions

Microsoft

IBM

Progress Software Corporation

Hibernating Rhinos

Initial release

2012

1989

2000

1984

2010

Current release

SQL Server 2022, November 2022

OpenEdge 12.2, March 2020

5.4, July 2022

License

Commercial or Open Source

Open Source

GPLv2

commercial

restricted free version is available

commercial

Open Source

AGPL version 3, commercial license 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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

C++

Server operating systems

server-less

Linux
Windows

Linux

included in appliance

AIX
HP-UX
Linux
Solaris
Windows

Linux
macOS
Raspberry Pi
Windows

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

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

yes

close to SQL 92

SQL-like query language (RQL)

APIs and other access methods

in-process shared library

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

JDBC
ODBC
OLE DB

JDBC
ODBC

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

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

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

C
C++
Fortran
Java
Lua
Perl
Python
R

Progress proprietary ABL (Advanced Business Language)

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

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

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

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

Sharding

horizontal partitioning

since Version 11.4

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, but depending on the SQL-Server Edition

Source-replica replication

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

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

ACID, Cluster-wide transaction available

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

Users and groups

Authorization levels configured per client per database

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.