DBMS > Amazon Redshift vs. Ingres vs. Quasardb vs. Teradata

System Properties Comparison Amazon Redshift vs. Ingres vs. Quasardb vs. Teradata

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Well established RDBMS

Distributed, high-performance timeseries database

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	3.80
Rank	#82	Overall
	#44	Relational DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Website

aws.amazon.com/redshift

www.actian.com/databases/ingres

quasar.ai

www.teradata.com

Technical documentation

docs.aws.amazon.com/redshift

docs.actian.com/ingres

doc.quasar.ai/master

docs.teradata.com

Developer

Amazon (based on PostgreSQL)

Actian Corporation

quasardb

Teradata

Initial release

2012

1974

originally developed at University Berkely in early 1970s

2009

1984

Current release

11.2, May 2022

3.14.1, January 2024

Teradata Vantage 1.0 MU2, January 2019

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

Server operating systems

hosted

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

BSD
Linux
OS X
Windows

hosted
Linux

Data scheme

yes

schema-free

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.

but tools for importing/exporting data from/to XML-files available

yes

Secondary indexes

restricted

yes

with tags

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like query language

yes

SQL 2016 + extensions

APIs and other access methods

JDBC
ODBC

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

HTTP API

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

All languages supporting JDBC/ODBC

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

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

consistent hashing

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Ingres Replicator

Source-replica replication with selectable replication factor

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

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

MVCC

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

yes

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

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.