DBMS > H2GIS vs. Infobright vs. Microsoft Azure SQL Database vs. SAP HANA

System Properties Comparison H2GIS vs. Infobright vs. Microsoft Azure SQL Database vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Spatial extension of H2

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Database as a Service offering with high compatibility to Microsoft SQL Server

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Spatial DBMS

Relational DBMS

Secondary database models

Relational DBMS

Document store
Graph DBMS
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.h2gis.org

ignitetech.com/softwarelibrary/infobrightdb

azure.microsoft.com/en-us/products/azure-sql/database

www.sap.com/products/hana.html

Technical documentation

www.h2gis.org/docs/home

docs.microsoft.com/en-us/azure/azure-sql

help.sap.com/hana

Developer

CNRS

Ignite Technologies Inc.; formerly InfoBright Inc.

Microsoft

SAP

Initial release

2013

2005

2010

Current release

V12

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

LGPL 3.0

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

Server operating systems

Linux
Windows

hosted

Appliance or cloud-service

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC

Supported programming languages

Java

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

based on H2

Transact SQL

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on H2

Source-replica replication

yes, with always 3 replicas available

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

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, multi-version concurrency control (MVCC)

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

yes

based on H2

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

fine grained access rights according to SQL-standard

yes

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.