Teradata

Teradata Overview
Teradata Architecture
Teradata Architecture Components
Teradata Feature components

Teradata Overview
Teradata acts as a single data store that accepts a large number of
concurrent request from multiple client applications
The main Integral part of Teradata is Parallel Processing Performance
It is the only database that distributes the loads data in Parallel, Backs-up
data in Parallel and Processes data in Parallel among several users
Execution of complex queries with a maximum of 256 joins
Complete scalability

Teradata Architecture

Answer Set Response

SQL Request
Session
Control

PE

Parser
Optimize
r
Dispatch
er
BYNET
0
AMP

Disk1

Message Passing Layer

AMP

AMP
Disk2

Disk3

Disk4

BYNET 1
AMP

SQL Request
SQL consists of:
Data Definition Language (DDL)

Defines database structures (tables, users, views, macros,

triggers, etc.)
CREATE

DROP

ALTER

Data Manipulation Language (DML)

Manipulates rows and data values

SELECT

INSERT

UPDATE

DELETE

Data Control Language (DCL)

Grants and revokes access rights
GRANT

REVOKE

Teradata SQL also includes Teradata Extensions to SQL

HELP

SHOW

EXPLAIN CREATE MACRO

Parsing Engine Elements

Parsing Engine Elements

Process

Session Control

It checks authorization of users

beforeprocessingany SQL query.
Manages session activities, such as logon,
password validation, and logoff.
Recovers sessions following client or
server
failures.

Parser

It checks syntax of the SQL query and

access rights to the user to access
variousdatabase objectsreferred in the
SQL query.

Optimizer

Determines the most efficient path to

access data

Dispatcher

Receives processing steps from the parser

and
sends them to the appropriate AMPs via the
BYNET
Monitors the completion of steps and
handles

BYNET:
The BYNET acts as a Message Passing Layer (MPL) and it handles the internal
communication of the Teradata RDBMS. All communication between PEs and AMPs is
done via the Message Passing Layer
It decides which AMP should receive a message
The BYNET software, and the BYNET interconnect itself.

Access Module Processor:

The Access Module Processor (AMP) is responsible for managing a portion of the
database. An AMP will control some portion of each table on the system
The Database Manager subsystem resides on each AMP. It receives the steps from the
Dispatcher and processes the steps.
AMP's work only on their own VDISK and do not have access to other AMP's VDISK.
Once the AMP performthe steps, it send back response to PE via BYNET where all the
responses from various AMP's is collected and sent back to user.
Each AMP is allowed to Read and Write in its own disk only. This is known as SHARED
NOTHING ARCHITECTURE
Disks:
Disks are disk drives associated with an AMP that store the data rows

Teradata Feature components

Parallelism
Scalability
speed

Teradata Parallelism
PE

PE
Session B

Session A

Message Passing Layer

AMP1
Task 1
Task 2

AMP2
Task 3
Task 4

AMP3

AMP4
Task 5
Task 6

Task 7
Task 8

scalability
One of the most important asset of Teradata is that it has scalability. The
Teradata DB scalability allow the system to grow as the business grow.
Any time do you want to double the speed of TD System, Just double the
no of AMP's and PE's.
PE

AMP

AMP

Disk

Disk

EMP Table
Id 1
Id 2
Id 3
Id - 4

EMP Table
Id 5
Id 6
Id 7
Id - 8

Scalability
TD
PE

AMP

AMP

Disk
EMP
Table
Id 1
Id - 2

Disk
EMP
Table
Id 3
Id - 4

AMP

Disk
EMP Table
Id 5
Id 6

AMP

Disk
EMP Table
Id 7
Id - 8