DBMS > Infobright vs. Ingres vs. SAP HANA vs. SiteWhere

System Properties Comparison Infobright vs. Ingres vs. SAP HANA vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Well established RDBMS

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

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Time Series DBMS

Secondary database models

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.88
Rank	#198	Overall
	#92	Relational DBMS

Score	3.63
Rank	#79	Overall
	#43	Relational DBMS

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Score	0.07
Rank	#347	Overall
	#33	Time Series DBMS

Website

ignitetech.com/softwarelibrary/infobrightdb

www.actian.com/databases/ingres

www.sap.com/products/hana.html

github.com/sitewhere/sitewhere

Technical documentation

docs.actian.com/ingres

help.sap.com/hana

sitewhere1.sitewhere.io/index.html

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

Actian Corporation

SAP

SiteWhere

Initial release

2005

1974

originally developed at University Berkely in early 1970s

2010

Current release

12.0, July 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

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

commercial

Open Source

Common Public Attribution License Version 1.0

Cloud-based only

Only available as a cloud service

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

Server operating systems

Linux
Windows

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Appliance or cloud-service

Linux
OS X
Windows

Data scheme

yes

predefined scheme

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.

but tools for importing/exporting data from/to XML-files available

Secondary indexes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

JDBC
ODBC

HTTP REST

Supported programming languages

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

Server-side scripts

Stored procedures

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Ingres Star to access multiple databases simultaneously

yes

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Ingres Replicator

yes

selectable replication factor

based on HBase

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

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

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

fine grained access rights according to SQL-standard

yes

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.