DBMS > Amazon Redshift vs. Quasardb vs. Teradata Aster vs. Tibero

System Properties Comparison Amazon Redshift vs. Quasardb vs. Teradata Aster vs. Tibero

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

Distributed, high-performance timeseries database

Platform for big data analytics on multistructured data sources and types

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	1.59
Rank	#148	Overall
	#68	Relational DBMS

Website

aws.amazon.com/redshift

quasar.ai

us.tmaxsoft.com/products/tibero

Technical documentation

docs.aws.amazon.com/redshift

doc.quasar.ai/master

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Amazon (based on PostgreSQL)

quasardb

Teradata

TmaxSoft

Initial release

2012

2009

2005

2003

Current release

3.14.1, January 2024

6, April 2015

License

Commercial or Open Source

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

commercial

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

C and Assembler

Server operating systems

hosted

BSD
Linux
OS X
Windows

Linux

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

yes

Typing

predefined data types such as float or date

yes

integer and binary

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

in Aster File Store

yes

Secondary indexes

restricted

yes

with tags

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC

HTTP API

ADO.NET
JDBC
ODBC
OLE DB

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

C
C#
C++
Java
Python
R

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

user defined functions

in Python

R packages

Persistent Stored Procedure (PSM)

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

consistent hashing

Sharding

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication with selectable replication factor

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using LevelDB

yes

In-memory capabilities

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

yes

Transient mode

planned for next version

User concepts

Access control

fine grained access rights according to SQL-standard

Cryptographically strong user authentication and audit trail

fine grained access rights according to SQL-standard

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.