DBMS > Manticore Search vs. Microsoft SQL Server vs. Postgres-XL vs. ToroDB

System Properties Comparison Manticore Search vs. Microsoft SQL Server vs. Postgres-XL vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Microsofts flagship relational DBMS

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Search engine

Relational DBMS

Document store

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

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

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Website

manticoresearch.com

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

www.postgres-xl.org

github.com/torodb/server

Technical documentation

manual.manticoresearch.com

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

www.postgres-xl.org/documentation

Developer

Manticore Software

Microsoft

8Kdata

Initial release

2017

1989

2014

since 2012, originally named StormDB

2016

Current release

6.0, February 2023

SQL Server 2022, November 2022

10 R1, October 2018

License

Commercial or Open Source

Open Source

GPL version 2

commercial

restricted free version is available

Open Source

Mozilla public license

Open Source

AGPL-V3

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

Java

Server operating systems

FreeBSD
Linux
macOS
Windows

Linux
Windows

Linux
macOS

All OS with a Java 7 VM

Data scheme

Fixed schema

yes

schema-free

Typing

predefined data types such as float or date

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

yes

string, integer, double, boolean, date, object_id

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

XML type, but no XML query functionality

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

yes

distributed, parallel query execution

APIs and other access methods

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

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

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

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

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

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

user defined functions

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

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

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

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication based on Galera library

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

Immediate Consistency

Eventual Consistency
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

MVCC

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

fine grained access rights according to SQL-standard

Access rights for users and roles

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.