DBMS > Manticore Search vs. SAP HANA vs. Transbase

System Properties Comparison Manticore Search vs. SAP HANA vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

In-memory, column based data store. Available as appliance or cloud service

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Search engine

Relational DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

manticoresearch.com

www.sap.com/products/hana.html

www.transaction.de/en/products/transbase.html

Technical documentation

manual.manticoresearch.com

help.sap.com/hana

www.transaction.de/en/products/transbase/features.html

Developer

Manticore Software

SAP

Transaction Software GmbH

Initial release

2017

2010

1987

Current release

6.0, February 2023

2.0 SPS07 (April 4, 2023), April 2023

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

GPL version 2

commercial

free development license

Cloud-based only

Only available as a cloud service

also available as a cloud based 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

FreeBSD
Linux
macOS
Windows

Appliance or cloud-service

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

Fixed schema

yes

Typing

predefined data types such as float or date

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

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

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

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

SQLScript, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication based on Galera library

yes

Source-replica replication

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

Transaction concepts

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

yes

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

User concepts

Access control

yes

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.