DBMS > AgensGraph vs. Manticore Search vs. Oracle vs. SAP Adaptive Server

System Properties Comparison AgensGraph vs. Manticore Search vs. Oracle vs. SAP Adaptive Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Multi-storage database for search, including full-text search.

Widely used RDBMS

The SAP (Sybase) Adaptive Server Enterprise (ASE) is an enterprise-class RDBMS

Primary database model

Graph DBMS
Relational DBMS

Search engine

Relational DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

Spatial DBMS

with Boeing's Spatial Query Server

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

Score	0.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	36.31
Rank	#25	Overall
	#17	Relational DBMS

Website

bitnine.net/agensgraph

manticoresearch.com

www.oracle.com/database

www.sap.com/products/technology-platform/sybase-ase.html

Technical documentation

bitnine.net/documentation

manual.manticoresearch.com

docs.oracle.com/en/database

help.sap.com/docs/SAP_ASE

Developer

Bitnine Global Inc.

Manticore Software

Oracle

SAP, Sybase

Initial release

2016

2017

1980

1987

Current release

2.1, December 2018

6.0, February 2023

23c, September 2023

16.0

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

GPL version 2

commercial

restricted free version is available

commercial

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

C and C++

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
macOS
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

AIX
HP-UX
Linux
Solaris
Unix
Windows

Data scheme

depending on used data model

Fixed schema

yes

Schemaless in JSON and XML columns

yes

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

yes

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like query language

yes

with proprietary extensions

yes

APIs and other access methods

Cypher Query Language
JDBC

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

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

Supported programming languages

C
Java
JavaScript
Python

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

C
C++
Cobol
Java
Java
Perl
PHP
Python

Server-side scripts

Stored procedures

yes

user defined functions

PL/SQL

also stored procedures in Java possible

Java and Transact-SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

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

Sharding, horizontal partitioning

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Synchronous replication based on Galera library

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

isolation level can be parameterized

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 Manticore index.

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

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.