DBMS > GridGain vs. Hive vs. JaguarDB vs. Microsoft SQL Server vs. Netezza

System Properties Comparison GridGain vs. Hive vs. JaguarDB vs. Microsoft SQL Server vs. Netezza

Editorial information provided by DB-Engines

Name

Description

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

data warehouse software for querying and managing large distributed datasets, built on Hadoop

Performant, highly scalable DBMS for AI and IoT applications

Microsofts flagship relational DBMS

Data warehouse and analytics appliance part of IBM PureSystems

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Key-value store
Vector DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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	62.59
Rank	#18	Overall
	#12	Relational DBMS

Score	0.09
Rank	#356	Overall
	#53	Key-value stores
	#13	Vector DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	10.18
Rank	#46	Overall
	#29	Relational DBMS

Website

www.gridgain.com

hive.apache.org

www.jaguardb.com

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

www.ibm.com/products/netezza

Technical documentation

www.gridgain.com/docs/index.html

cwiki.apache.org/confluence/display/Hive/Home

www.jaguardb.com/support.html

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

Developer

GridGain Systems, Inc.

Apache Software Foundation

initially developed by Facebook

DataJaguar, Inc.

Microsoft

IBM

Initial release

2007

2012

2015

1989

2000

Current release

GridGain 8.5.1

3.1.3, April 2022

3.3 July 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

GPL V3.0

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

Java, C++, .Net

Java

C++

the server part. Clients available in other languages

C++

Server operating systems

Linux
OS X
Solaris
Windows

All OS with a Java VM

Linux

Linux
Windows

Linux

included in appliance

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

SQL

Support of SQL

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

SQL-like DML and DDL statements

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

APIs and other access methods

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

JDBC
ODBC
Thrift

JDBC
ODBC

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

JDBC
ODBC
OLE DB

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C++
Java
PHP
Python

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

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

C
C++
Fortran
Java
Lua
Perl
Python
R

Server-side scripts

Stored procedures

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

yes

user defined functions and integration of map-reduce

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

selectable replication factor

Multi-source replication

yes, but depending on the SQL-Server Edition

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

yes

query execution via MapReduce

yes

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Access rights for users, groups and roles

rights management via user accounts

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.