DBMS > Geode vs. IBM Db2 vs. Microsoft SQL Server vs. mSQL

System Properties Comparison Geode vs. IBM Db2 vs. Microsoft SQL Server vs. mSQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Common in IBM host environments, 2 different versions for host and Windows/Linux

Microsofts flagship relational DBMS

mSQL (Mini SQL) is a simple and lightweight RDBMS

Primary database model

Key-value store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Relational DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

Document store
Graph DBMS
Spatial DBMS

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

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	128.46
Rank	#8	Overall
	#5	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Website

geode.apache.org

www.ibm.com/products/db2

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

hughestech.com.au/products/msql

Technical documentation

geode.apache.org/docs

www.ibm.com/docs/en/db2

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

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

IBM

Microsoft

Hughes Technologies

Initial release

2002

1983

host version

1989

1994

Current release

1.1, February 2017

12.1, October 2016

SQL Server 2022, November 2022

4.4, October 2021

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

free version is available

commercial

restricted free version is available

commercial

free licenses can be provided

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

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

schema-free

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

SQL-like query language (OQL)

yes

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

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

JDBC
ODBC

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

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

C
C++
Delphi
Java
Perl
PHP
Tcl

Server-side scripts

Stored procedures

user defined functions

yes

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

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

with separate tools (MQ, InfoSphere)

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

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

Access rights per client and object definable

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.