DBMS > Netezza vs. Oracle vs. PlanetScale vs. Sadas Engine

System Properties Comparison Netezza vs. Oracle vs. PlanetScale vs. Sadas Engine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Data warehouse and analytics appliance part of IBM PureSystems

Widely used RDBMS

Scalable, distributed, serverless MySQL database platform built on top of Vitess

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

Relational DBMS

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

Document store
Spatial DBMS

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

Score	8.59
Rank	#45	Overall
	#29	Relational DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Website

www.ibm.com/products/netezza

www.oracle.com/database

planetscale.com

www.sadasengine.com

Technical documentation

docs.oracle.com/en/database

planetscale.com/docs

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

IBM

Oracle

PlanetScale

SADAS s.r.l.

Initial release

2000

1980

2020

2006

Current release

23c, September 2023

8.0

License

Commercial or Open Source

commercial

restricted free version is available

commercial

free trial version available

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

C++

Server operating systems

Linux

included in appliance

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

Docker
Linux
macOS

AIX
Linux
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

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC
OLE DB

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

ADO.NET
JDBC
MySQL protocol
ODBC

JDBC
ODBC
Proprietary protocol

Supported programming languages

C
C++
Fortran
Java
Lua
Perl
Python
R

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

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

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

yes

PL/SQL

also stored procedures in Java possible

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

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

isolation level can be parameterized

ACID at shard level

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

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

yes

managed by 'Learn by Usage'

User concepts

Access control

Users with fine-grained authorization concept

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

Access rights for users, groups and roles according to SQL-standard

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.