DBMS > GridGain vs. JaguarDB vs. Manticore Search vs. Microsoft SQL Server

System Properties Comparison GridGain vs. JaguarDB vs. Manticore Search vs. Microsoft SQL Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

GridGain is an in-memory computing platform, built on Apache Ignite

Performant, highly scalable DBMS for AI and IoT applications

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

Microsofts flagship relational DBMS

Primary database model

Key-value store
Relational DBMS

Key-value store
Vector DBMS

Search engine

Relational DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store
Graph DBMS
Spatial DBMS

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

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

www.gridgain.com

www.jaguardb.com

manticoresearch.com

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

Technical documentation

www.gridgain.com/docs/index.html

www.jaguardb.com/support.html

manual.manticoresearch.com

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

Developer

GridGain Systems, Inc.

DataJaguar, Inc.

Manticore Software

Microsoft

Initial release

2007

2015

2017

1989

Current release

GridGain 8.5.1

3.3 July 2023

6.0, February 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

Open Source

GPL version 2

commercial

restricted free version is 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.

Implementation language

Java, C++, .Net

C++

the server part. Clients available in other languages

C++

Server operating systems

Linux
OS X
Solaris
Windows

Linux

FreeBSD
Linux
macOS
Windows

Linux
Windows

Data scheme

yes

Fixed schema

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.

yes

Can index from XML

yes

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like query language

yes

APIs and other access methods

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

JDBC
ODBC

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

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

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

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

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

user defined functions

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

Triggers

yes (cache interceptors and events)

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Multi-source replication

Synchronous replication based on Galera library

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

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

ACID

yes

isolated transactions for atomic changes and binary logging for safe writes

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

User concepts

Access control

Security Hooks for custom implementations

rights management via user accounts

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.