DBMS > Infobright vs. Oracle vs. PostGIS vs. Sphinx

System Properties Comparison Infobright vs. Oracle vs. PostGIS vs. Sphinx

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

Widely used RDBMS

Spatial extension of PostgreSQL

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Relational DBMS

Spatial DBMS

Search engine

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

Relational DBMS

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

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

ignitetech.com/softwarelibrary/infobrightdb

www.oracle.com/database

postgis.net

sphinxsearch.com

Technical documentation

docs.oracle.com/en/database

postgis.net/documentation

sphinxsearch.com/docs

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

Oracle

Sphinx Technologies Inc.

Initial release

2005

1980

2005

2001

Current release

23c, September 2023

3.4.2, February 2024

3.5.1, February 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

restricted free version is available

Open Source

GPL v2.0

Open Source

GPL version 2, commercial licence available

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++

C++

Server operating systems

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

Schemaless in JSON and XML columns

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

Knowledge Grid Technology used instead

yes

full-text index on all search fields

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL-like query language (SphinxQL)

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Proprietary protocol

Supported programming languages

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

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding, horizontal partitioning

yes

based on PostgreSQL

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

none

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

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

isolation level can be parameterized

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

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

based on PostgreSQL

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.