DBMS > IBM Db2 vs. Infobright vs. OrigoDB vs. Snowflake

System Properties Comparison IBM Db2 vs. Infobright vs. OrigoDB vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

A fully ACID in-memory object graph database

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Relational DBMS

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

Relational DBMS

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Document store
RDF store

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

with Db2 Spatial Extender

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

Score	125.90
Rank	#9	Overall
	#6	Relational DBMS

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.ibm.com/products/db2

ignitetech.com/softwarelibrary/infobrightdb

origodb.com

www.snowflake.com

Technical documentation

www.ibm.com/docs/en/db2

origodb.com/docs

docs.snowflake.net/manuals/index.html

Developer

IBM

Ignite Technologies Inc.; formerly InfoBright Inc.

Robert Friberg et al

Snowflake Computing Inc.

Initial release

1983

host version

2005

2009

under the name LiveDB

2014

Current release

12.1, October 2016

License

Commercial or Open Source

commercial

free version is available

commercial

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

Open Source

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C and C++

Server operating systems

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Linux
Windows

hosted

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

yes

Secondary indexes

yes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

ADO.NET
JDBC
ODBC

.NET Client API
HTTP API
LINQ

CLI Client
JDBC
ODBC

Supported programming languages

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

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

.Net

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

Domain Events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

none

horizontal partitioning

client side managed; servers are not synchronized

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

with separate tools (MQ, InfoSphere)

Source-replica replication

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

depending on model

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

Write ahead log

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

Role based authorization

Users with fine-grained authorization concept, user roles and pluggable authentication

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.