DBMS > IBM Db2 vs. SQLite vs. Transbase vs. Warp 10

System Properties Comparison IBM Db2 vs. SQLite vs. Transbase vs. Warp 10

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

Widely used embeddable, in-process RDBMS

A resource-optimized, high-performance, universally applicable RDBMS

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Relational DBMS

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

Relational DBMS

Time Series 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	128.46
Rank	#8	Overall
	#5	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

www.ibm.com/products/db2

www.sqlite.org

www.transaction.de/en/products/transbase.html

www.warp10.io

Technical documentation

www.ibm.com/docs/en/db2

www.sqlite.org/docs.html

www.transaction.de/en/products/transbase/features.html

www.warp10.io/content/02_Getting_started

Developer

IBM

Dwayne Richard Hipp

Transaction Software GmbH

SenX

Initial release

1983

host version

2000

1987

2015

Current release

12.1, October 2016

3.45.3 (15 April 2024), April 2024

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

free version is available

Open Source

Public Domain

commercial

free development license

Open Source

Apache License 2.0

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

C and C++

Java

Server operating systems

AIX
HP-UX
Linux
Solaris
Windows
z/OS

server-less

FreeBSD
Linux
macOS
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

dynamic column types

yes

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

yes

APIs and other access methods

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API
Jupyter
WebSocket

Supported programming languages

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

with separate tools (MQ, InfoSphere)

none

Source-replica replication

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

based on HBase

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.