Download as PPT, PDF, TXT or read online from Scribd
Download as ppt, pdf, or txt
You are on page 1/ 11
Module 4: Teradata RDBMS Architecture
After completing this module, you will be able to:
Describe the purpose of the PE and the AMP. Describe the overall RDBMS parallel architecture. Describe the relationship of the RDBMS to its client side applications.
Teradata and MPP Systems
Teradata is the software that makes a MPP system appear to be a single system to users and administrators. BYNET 0 The two major components of the Teradata RBDMS are implemented as virtual processors (vproc).
BYNET 1
PE
PE
PE
PE
PE
PE
PE
PE
Parsing Engine (PE)
Access Module
AMP
AMP
AMP
AMP
AMP
AMP
AMP
AMP
Processor (AMP)
AMP
AMP
AMP
AMP
AMP
AMP
AMP
AMP
AMP
AMP
AMP
AMP
AMP
AMP
AMP
AMP
AMP
AMP
AMP
AMP
AMP
AMP
AMP
AMP
The MPL (PDE and BYNET)
connects multiple nodes together and allows Teradata to communicate between nodes.
O.S.
O.S.
O.S.
O.S.
Node 0
Node 1
Node 2
Node 3
Teradata Functional Overview
Channel-Attached System
Network-Attached System
Client Application
Client Application
CLI
CLI or ODBC
Teradata RDBMS Channel
TDP
Parsing Engine
LAN
Parsing Engine
MTDP
MOSI Message Passing Layer
AMP
AMP
AMP
AMP
Channel-Attached Client Software Overview
Channel-Attached System Client Application
Client Application
CLI
CLI
Channel (ESCON or Bus/Tag)
Host Channel Adapter
PBSA or PBCA
TDP
Client Application - Your own application(s) - Teradata utilities (BTEQ, etc.)
Parsing Engine
CLI (Call-Level Interface) Service Routines
- Request and Response Control - Parcel creation and blocking/unblocking - Buffer allocation and initialization TDP (Teradata Director Program) - Session balancing across multiple PEs - Insures proper message routing to/from RDBMS - Failure notification (application failure, Teradata restart)
- Library of routines for blocking/unblocking requests and responses to/from the RDBMS
ODBC (Open Database Connectivity) Driver
- Uses open standards-based ODBC interface to provide client applications access to Teradata MTDP (Micro Teradata Director Program) - Library of session management routines MOSI (Micro Operating System Interface) - Library of routines providing OS independent interface
The Parsing Engine
Answer Set Response
SQL Request
The Parsing Engine is responsible for:
Managing individual sessions (up
Parser
to 120) Parsing Engine
Parsing and Optimizing your SQL
Optimizer
requests
Dispatching the optimized plan to
Dispatcher
the AMPs
Input conversion (EBCDIC / ASCII)
- if necessary
Message Passing Layer
Sending the answer set response
AMP
AMP
AMP
AMP
back to the requesting client
Message Passing Layer
SQL Request
Answer Set Response
The Message Passing Layer is
responsible for:
Carrying messages between the AMPs
and PEs
Parsing Engine
Point-to-Point, Multi-Cast, and
Broadcast communications
Merging answer sets back to the PE
Making Teradata parallelism possible
Message Passing Layer
(PDE and BYNET)
The Message Passing Layer is a
combination of: AMP
AMP
AMP
AMP
Parallel Database Extensions (PDE)
Software
BYNET Software BYNET Hardware for MPP systems
The Access Module Processor (AMP)
SQL Request
Answer Set Response
Parsing Engine
Message Passing Layer
AMP
AMP
AMP
AMP
AMPs store and retrieve rows to and from disk
The AMPs are responsible for:
Finding the rows requested Lock management Sorting rows Aggregating columns Join processing Output conversion and formatting Creating answer set for client Disk space management Accounting Special utility protocols Recovery processing
Teradata Parallelism PE
PE
PE
Session A
Session C
Session E
Session B
Session D
Session F
Message Passing Layer
AMP 1
AMP 2
Task 1 Task 2 Task 3
Task 4 Task 5 Task 6
AMP 3 Task 7 Task 8 Task 9
AMP 4
Parallelism is built into
Teradata from the ground up!
Task 10 Task 11 Task 12
Notes:
Each PE can handle up to 120 sessions in parallel.
Each Session can handle multiple REQUESTS. The Message Passing Layer can handle all message activity in parallel. Each AMP can perform up to 80 tasks in parallel. All AMPs can work together in parallel to service any request. Each AMP can work on several requests in parallel.
Review Questions 1. What are the two software elements that accompany an application on all client side environments? 2. What is the purpose of the PE? 3. What is the purpose of the AMP? 4. How many sessions can a PE support? Match Quiz ____ 1. CLI
h. PE S/W sends plan steps to AMP i. Library of Teradata Service Routines j. Foundation of Teradata architecture
Module 4: Review Question Answers
1. What are the two software elements that accompany an application on all client side environments? CLI/ODBC and TDP/MTDP 2. What is the purpose of the PE? Parse, optimize, and dispatch queries 3. What is the purpose of the AMP? Manage and retrieve data from disk storage 4. How many sessions can a PE support? 120 Match Quiz __i_ 1. CLI
