DBMS > GridGain vs. Microsoft SQL Server vs. Sphinx vs. TerminusDB

System Properties Comparison GridGain vs. Microsoft SQL Server vs. Sphinx vs. TerminusDB

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

Microsofts flagship relational DBMS

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

Key-value store
Relational DBMS

Relational DBMS

Search engine

Graph DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
RDF store

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

Score	1.53
Rank	#155	Overall
	#26	Key-value stores
	#73	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	6.03
Rank	#60	Overall
	#6	Search engines

Score	0.22
Rank	#323	Overall
	#28	Graph DBMS

Website

www.gridgain.com

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

sphinxsearch.com

terminusdb.com

Technical documentation

www.gridgain.com/docs/index.html

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

sphinxsearch.com/docs

terminusdb.github.io/terminusdb/#

Developer

GridGain Systems, Inc.

Microsoft

Sphinx Technologies Inc.

DataChemist Ltd.

Initial release

2007

1989

2001

2018

Current release

GridGain 8.5.1

SQL Server 2022, November 2022

3.5.1, February 2023

11.0.0, January 2023

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

GPL version 2, commercial licence available

Open Source

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

Implementation language

Java, C++, .Net

C++

Prolog, Rust

Server operating systems

Linux
OS X
Solaris
Windows

Linux
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

yes

full-text index on all search fields

SQL

Support of SQL

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

yes

SQL-like query language (SphinxQL)

SQL-like query language (WOQL)

APIs and other access methods

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

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

Proprietary protocol

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

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

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

JavaScript
Python

Server-side scripts

Stored procedures

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

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

yes

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

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 (replicated cache)

yes, but depending on the SQL-Server Edition

none

Journaling Streams

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

Foreign keys

Referential integrity

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

Security Hooks for custom implementations

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.