DBMS > Linter vs. Oracle vs. PlanetScale vs. SAP HANA vs. Transbase

System Properties Comparison Linter vs. Oracle vs. PlanetScale vs. SAP HANA vs. Transbase

Editorial information provided by DB-Engines

Name

Description

RDBMS for high security requirements

Widely used RDBMS

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

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

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

Primary database model

Relational DBMS

Secondary database models

Spatial DBMS

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

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

linter.ru

www.oracle.com/database

planetscale.com

www.sap.com/products/hana.html

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

Technical documentation

docs.oracle.com/en/database

planetscale.com/docs

help.sap.com/hana

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

Developer

relex.ru

Oracle

PlanetScale

SAP

Transaction Software GmbH

Initial release

1990

1980

2020

2010

1987

Current release

23c, September 2023

2.0 SPS07 (April 4, 2023), April 2023

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

restricted free version is available

commercial

free development license

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

C and C++

Server operating systems

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

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

Docker
Linux
macOS

Appliance or cloud-service

FreeBSD
Linux
macOS
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

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

ADO.NET
JDBC
MySQL protocol
ODBC

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
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

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

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

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

PL/SQL

also stored procedures in Java possible

yes

proprietary syntax

SQLScript, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding, horizontal partitioning

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

yes

Source-replica replication

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

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

ACID

yes

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

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

yes

fine grained access rights 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.