Professional Documents
Culture Documents
Initially, the data warehouse was a historical database, enterprise-wide and centralized,
containing data derived from an operational database.
The data in the data warehouse was:
• Subject-oriented
• Integrated
• Usually identified by a timestamp
• Nonvolatile, that is, nothing was added or removed
Rows in the tables supporting the operational database were loaded into the data warehouse (The
historical database) after they exceeded some well-defined date.
Data could be queried, but the responses returned only reflected historical information. In this
sense, a data warehouse was initially static, and even if a historical data warehouse contained
data that was being updated, it would still not be an active data warehouse.
Strategic queries represent business questions that are intended to draw strategic advantage
from large stores of data. Strategic queries are often complex queries.
Tactical queries are short, highly tuned that facilitate action-taking or decision-making in a
time-sensitive environment.
Tactical queries are usually repetitively executed and take advantage of techniques such as
request (query plan) caching and session-pooling.
Teradata Database
The Teradata Database is an information repository supported by tools and utilities that make it,
as part of the Teradata Warehouse, a complete and active relational database management
system.
Capacity includes:
Parallel processing: makes Teradata Database faster than other relational systems.
Data integrity: ensures that transactions either complete or rollback to a stable state if a
fault occurs.
The BYNET is the combination of hardware and software that enables the high speed
communication inside and between the nodes.
Linear Scalability:
Fault Tolerance:
Load Balancing:
Enhanced Performance: By default, a Teradata MPP system is equipped with two
BYNET networks. Since both BYNET networks in a system are active, the system
performance can be enhanced by using the combined bandwidth of the two networks.
Messages:
Point-to-Point - A virtual proc can send a message to another virtual proc:
In the same node using BYNET software only, the message is reassigned in memory to the target
virtual proc.
In another node the message is using both BYNET hardware and software.
Multicast - A virtual proc can send a message to multiple virtual proc by sending a broadcast
message to all nodes. The BYNET software on the receiving node determines whether a virtual
proc on the node should receive or discard the message.
Broadcast - A virtual proc can broadcast a message to all the virtual proc in the system.
1. UNIX operating system - The Teradata RDBMS runs on UNIX SVR4 with MP-RAS.
2.
3. Parallel Database Extensions (PDE) - PDE was added to the UNIX kernel by NCR to support
the parallel software environment.
4.
5. Trusted Parallel Application (TPA) - A TPA uses PDE to implement virtual processors. The
Teradata RDBMS is classified as a TPA.
6.
7. Channel Driver - The Channel Driver software is the means of communication between the
application and the PEs assigned to channel-attached clients.
8. Teradata Gateway - The Gateway software is the means of communication between the
application and the PEs assigned to network-attached clients. There is one Gateway per node.
9.
AMP
The AMP is a type of virtual proc that has software to manage data.
10.
1. AMP Worker Task (AWT) Functions in the AMP perform a number of operations, including:
1. Locking Tables
2. Executing Tables
3. Joining Tables
4. Executing end transaction steps
5.
2. The file system software accesses the data on the virtual disks. Each AMP uses the file system
software to read from and write to the virtual disks.
3.
4. Console Utilities - The AMP software includes utilities to perform generally sophisticated, low-
level functions such as:
1. Configure and reconfigure the system
2. Rebuild tables
3. Reveal details about locks and space status
Parsing Engine
PE is a type of virtual proc that has software components to break SQL into steps, and send the
steps to the AMPs.
5. Session Control - When you log on to the Teradata RDBMS through your application, the
session control software on the PE establishes that session. Session control also manages and
terminates sessions on the PE.
6.
7. Parser/Optimizer - The parser interprets your Teradata SQL request and checks the syntax.
The parser decomposes the request into AMP steps, using the optimizer to determine the most
efficient way to access the data on the virtual disks. Then the parser sends the steps to the
dispatcher.
8.
9. Dispatcher - The dispatcher is responsible for a number of tasks, depending on the operation it
is performing:
1. Processing Requests
2. Processing Responses