DBMS > MySQL vs. Netezza vs. Postgres-XL vs. UniData,UniVerse

System Properties Comparison MySQL vs. Netezza vs. Postgres-XL vs. UniData,UniVerse

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used open source RDBMS

Data warehouse and analytics appliance part of IBM PureSystems

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

MultiValue database and application server with SQL mapping layer and meta database capabilities

Primary database model

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Multivalue DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	7.56
Rank	#48	Overall
	#31	Relational DBMS

Score	0.43
Rank	#260	Overall
	#119	Relational DBMS

Score	2.25
Rank	#112	Overall
	#2	Multivalue DBMS

Website

www.mysql.com

www.ibm.com/products/netezza

www.postgres-xl.org

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

Technical documentation

dev.mysql.com/doc

www.postgres-xl.org/documentation

docs.rocketsoftware.com/bundle?cluster=true&labelkey=unidata&labelkey=prod_unidata

Developer

Oracle

since 2010, originally MySQL AB, then Sun

IBM

Rocket Software

Initial release

1995

2000

2014

since 2012, originally named StormDB

1985

Current release

9.0.0, July 2024

10 R1, October 2018

License

Commercial or Open Source

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

Mozilla public license

commercial

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

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

Linux

included in appliance

Linux
macOS

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

distributed, parallel query execution

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC
OLE DB

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Java API

JPA
JDBC
ODBC
OLE DB
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Fortran
Java
Lua
Perl
Python
R

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

.Net
Basic

U2 Basic
C
Java

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

user defined functions

yes

Triggers

yes

U2 Basic

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

MVCC

ACID

configurable

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

Users with fine-grained authorization concept

fine grained access rights according to SQL-standard

Access rights according to SQL-standard and operating system based

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.