DBMS > GeoSpock vs. Interbase vs. OpenQM vs. SAP HANA

System Properties Comparison GeoSpock vs. Interbase vs. OpenQM vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Spatial and temporal data processing engine for extreme data scale

Light-weight proven RDBMS

originally from Borland

QpenQM is a high-performance, self-tuning, multi-value DBMS

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

Primary database model

Relational DBMS

Multivalue DBMS

Relational DBMS

Secondary database models

Time Series 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	3.78
Rank	#77	Overall
	#41	Relational DBMS

Score	0.28
Rank	#291	Overall
	#10	Multivalue DBMS

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Website

geospock.com

www.embarcadero.com/products/interbase

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.sap.com/products/hana.html

Technical documentation

docs.embarcadero.com/products/interbase

help.sap.com/hana

Developer

GeoSpock

Embarcadero

Rocket Software, originally Martin Phillips

SAP

Initial release

1984

1993

2010

Current release

2.0, September 2019

InterBase 2020, December 2019

3.4-12

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

GPLv2, extended commercial license available

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, Javascript

Server operating systems

hosted

Android
iOS
Linux
OS X
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Appliance or cloud-service

Data scheme

yes

with some exceptions

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.

export as XML data possible

yes

Secondary indexes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC

JDBC
ODBC

Supported programming languages

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

.Net
Basic
C
Java
Objective C
PHP
Python

Server-side scripts

Stored procedures

yes

Interbase procedure and trigger language

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Interbase Change Views

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

Multiversion concurreny control

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 for users can be defined per table

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

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.