DBMS > Amazon Redshift vs. OpenEdge vs. SAP SQL Anywhere vs. Sphinx vs. TerminusDB

System Properties Comparison Amazon Redshift vs. OpenEdge vs. SAP SQL Anywhere vs. Sphinx vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Application development environment with integrated database management system

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Open source search engine for searching in data from different sources, e.g. relational databases

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Relational DBMS

Search engine

Graph DBMS

Secondary database models

Document store
RDF store

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	3.75
Rank	#88	Overall
	#47	Relational DBMS

Score	4.57
Rank	#78	Overall
	#43	Relational DBMS

Score	6.03
Rank	#60	Overall
	#6	Search engines

Score	0.22
Rank	#323	Overall
	#28	Graph DBMS

Website

aws.amazon.com/redshift

www.progress.com/openedge

www.sap.com/products/technology-platform/sql-anywhere.html

sphinxsearch.com

terminusdb.com

Technical documentation

docs.aws.amazon.com/redshift

documentation.progress.com/output/ua/OpenEdge_latest

help.sap.com/docs/SAP_SQL_Anywhere

sphinxsearch.com/docs

terminusdb.github.io/terminusdb/#

Developer

Amazon (based on PostgreSQL)

Progress Software Corporation

SAP

formerly Sybase

Sphinx Technologies Inc.

DataChemist Ltd.

Initial release

2012

1984

1992

2001

2018

Current release

OpenEdge 12.2, March 2020

17, July 2015

3.5.1, February 2023

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2, commercial licence available

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

hosted

AIX
HP-UX
Linux
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux

Data scheme

yes

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

Secondary indexes

restricted

yes

full-text index on all search fields

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

close to SQL 92

yes

SQL-like query language (SphinxQL)

SQL-like query language (WOQL)

APIs and other access methods

JDBC
ODBC

ADO.NET
HTTP API
JDBC
ODBC

Proprietary protocol

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

All languages supporting JDBC/ODBC

Progress proprietary ABL (Advanced Business Language)

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

yes, in C/C++, Java, .Net or Perl

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

since Version 11.4

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Database mirroring

none

Journaling Streams

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

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

yes

in-memory journaling

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 and groups

fine grained access rights according to SQL-standard

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