[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DEC Rdb against the World |
|
| Moderator: | HERON::GODFRIND |
|
| Created: | Fri Jun 12 1987 |
| Last Modified: | Thu Feb 23 1995 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1348 |
| Total number of notes: | 5438 |
914.0. "teradata dbc/1012 v3.2" by DATABS::JOEDAD::NEEDLEMAN (today nas/is, tomorrow...) Fri Apr 19 1991 16:18
From: SELL3::CIS_PROD "18-Apr-1991 1042" 18-APR-1991 10:40:01.64
To: PBSVAX::NEEDLEMAN
CC:
Subj: CIS DELIVERS ... DBC/1012 Model 3, Software Release 3.2, from Teradata
----- DBC/1012 Model 3, Software Release 3.2,
|C I S| from Teradata
-----
Author: Alban, H. Source : MIC
Type : Research Service
Date : 01-mAY-90
Report ID: 3017653
Section Topic
------- -----------------------------------------------------------------------
Intro Summary of Report (Supplied by CIS Editor)
1 The DBC/1012 Is a Database Machine
2 DBC/1012 Components
3 Hardware
4 Disk Storage Units (DSUS)
5 Connectivity
6 Subsystems - Host Interface Software
7 Interface Processors
8 Communication Processors
9 Access Module Processors
10 Ynet
11 Database Architecture
12 Integrity/Security
13 User Authorization
14 System Performance
15 Evaluation
16 Cooperative Processing
17 Broadening the Product Line
18 Weaknesses
19 Conclusions
+ - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - +
| Please be advised that the information contained within this |
+ report is copyrighted material. The following policies must +
| be adhered to: |
+ +
| - No reformatting of the data segments |
+ - No external distribution +
| - Internal use only in accordance with vendor agreements |
+ - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - +
MIC
( 1 )
----- DBC/1012 Model 3, Software Release 3.2, | 01-mAY-90
|C I S| from Teradata | MIC
-----
Intro: Summary of Report (Supplied by CIS Editor)
Teradata's DBC/1012 is a database machine, a special-purpose computer
optimized for relational database processing. It uses dedicated hardware and
software exclusively for database activities. The database machine is usually
attached to a host machine which provides the user interface and performs
other functions. The DBC/1012 implements true parallel processing. Multiple
microcomputer chips (Intel i286 and i386) perform the various subtasks
involved in responding to a query. The DBC/1012 has a layered structure.
Each module in this structure contains both hardware and software components,
and each has a specialized function. Each function is supported by one or
more dedicated micro-processors that are specially programmed for these tasks.
These function-specific processors are as follows: Interface Processors,
Communication Processors, and Access Module Processors.
Section: 1 The DBC/1012 Is a Database Machine
Teradata's DBC/1012 is a database machine, that is, a special-purpose computer
optimized for relational database processing. It uses dedicated hardware and
software exclusively for database activities. The database machine is usually
attached to a host machine which provides the user interface and performs
other functions.
Database machines are not intended to replace database management systems that
run on general-purpose computers. They are designed for special environments,
for large database applications that call for frequent relational joins.
The DBC/1012 implements true parallel processing. Multiple microcomputer
chips (Intel i286 and i386) perform the various subtasks involved in
responding to a query. Each processing request is subdivided into smaller
tasks which are distributed among the multiple processors. The more
processors and disks, the faster the response.
The DBC/1012 has a layered structure (see Figure 1 - unavailable in electronic
version). Each module in this structure contains both hardware and software
components, and each has a specialized function. At the highest level is the
host-resident software that accepts requests from users and applications.
These requests are transferred to the Teradata machine through either
interface processors (if the host is a workstation or LAN) or communication
processors (it the host is a mainframe). The requests are then parsed,
analyzed to determine what records are required, and passed to Ynet. Ynet
broadcasts the parsed statements to the AMPs, which directly access the disk
storage units and perform operations (such as sorting) as far as possible.
The AMPs then return the data to Ynet. Ynet coordinates the responses of the
MIC
( 2 )
----- DBC/1012 Model 3, Software Release 3.2, | 01-mAY-90
|C I S| from Teradata | MIC
-----
AMPs as necessary, then returns the response to the interface or communication
processor.
Section: 2 DBC/1012 Components
The DBC/1012 is composed of a set of modular components, or subsystems. Each
function is supported by one or more dedicated micro-processors that are
specially programmed for these tasks. These function-specific processors are
as follows: Interface Processors, Communication Processors, and Access Module
Processors.
The modular structure of the DBC/1012 contains the following subsystems:
o Host or workstation interface software
o Interface Processors (IFPs)
o Communication Processors (COPs)
o Access Module Processors (AMPs)
o Disk Storage Units (DSUs)
o System console
o Ynet interconnect logic
The processors of these subsystems are connected by two fully redundant Ynets
that can interconnect up to 1,024 processors. Ynet is a tree-structured
network of packet-sorting elements.
Section: 3 Hardware
DBC/1012 is available in two models: the i286-based Model 2 and the i386-based
Model 3.
Model 3 processor modules (AMPs, IFPs, and COPs) are equipped as follows:
o i386 microprocessor (20MHz)
o i387 numeric coprocessor (20MHZ)
o 64KB set-associative, high-speed cache for zero wait states
MIC
( 3 )
----- DBC/1012 Model 3, Software Release 3.2, | 01-mAY-90
|C I S| from Teradata | MIC
-----
o 4MB of Dynamic Random Access (DRAM) memory with 100 nanosecond response time
and surface mount technology (SMT)
o up to 4MB additional memory (optional)
o non-volatile disk cache (battery backed-up memory; optional). The disk
cache, which will be supported in DBC/1012 software Release 4.0, increases
the effective disk I/O bandwidth by providing a holding area for frequently
updated blocks such as journal buffers. It also can be used to defer and
even eliminate disk writes.
o TI 74AS632 chip for main memory error detection and correction
IFPs have an 8089A microcontroller for channel I/O. AMPs have Signetics 8X400
microcontrollers for disk I/O.
Data transfers between I/O controllers and main memory use a Direct Memory
Access (DMA) method over a 16MB/sec memory bus with automatic cache references
when required.
Section: 4 Disk Storage Units (DSUS)
DBC/1012 uses high-speed, large-volume, Winchester-type disk storage units.
Each disk is formatted to include areas for data storage, system work areas,
and optional fallback areas where critical data may be intentionally
duplicated. DSUs are available with 500MB capacity or 1.2 gigabyte (GB)
capacity.
The system can be configured to support either industry-standard Storage
Module Devices or Intelligent Peripheral Interface (IPI) interfaces.
Section: 5 Connectivity
DBC/1012 can connect to either mainframes or to workstations. It communicates
with mainframes using block multiplexer channels, and it communicates with
workstations using a local area network (LAN). Multiple hosts can share a
single DBC/1012 machine.
Teradata supplies interface software to the following hosts: MVS, MVS/XA,
MVS/ESA, VM/CMS, TPF, Unisys OS1100, Honeywell GCOS8, DEC VAX/VMS, UNIX, and
MS-DOS. Apple Macintosh computers can also serve as hosts to the DBC/1012. A
direct interface to the Unisys Mapper system is also available.
Teradata supports the Ethernet Local Area Network interface with TCP/IP,
MIC
( 4 )
----- DBC/1012 Model 3, Software Release 3.2, | 01-mAY-90
|C I S| from Teradata | MIC
-----
ISO/OSI, and XNS (for Metaphor) protocols. Teradata is also building gateways
to DECnet, NetBIOS, and Token Ring. The gateways are not identical to the
direct support described above. With direct support, requests are sent
directly through the Teradata host software to the database machine. Without
direct support, a front-end box to DECnet is required: e.g., SQL puts it on
DECnet, sends it to a machine running gateway software, and sends it out the
back end to the other end of the communication.
Section: 6 Subsystems - Host Interface Software
The Teradata Director Program (TDP) resides on the host. It manages the
channel activity while servicing request/response traffic from users and/or
application programs. TDP is re-entrant and, therefore, capable of directing
multiple sessions of activity concurrently.
When multiple hosts share a single machine, each host machine runs its own
TDP.
The TDP accepts requests through a Call Level Interface. The following tools
from Teradata can manage this Call Level Interface:
o Interactive Teradata Query (ITEQ): permits interactive terminal users to
establish a direct DBC/SQL dialogue with the DBC/ 1012
o Batch Teradata Query (BTEQ): accepts DBC/SQL commands to retrieve and format
data into reports, as well as to import or export data to and from host
files
o COBOL and PL/1 Preprocessors: programmer aids that permit DBC/SQL statements
to be embedded in source code. They can be used for batch programs or
online applications running under IBM's Customer Information Control
System (CICS) or Information Management System (IMS).
o Database Administration Utilities: utilities for dumping, restoring, and
loading databases.
o Transparency Series: software products that allow SQL requests originally
targeted for other database management systems (e.g., DB2) to access the
DBC/1012.
o WINCLI: allows MS-DOS users to access DBC/1012 through Microsoft Excel.
Users develop SQL statements in an Excel macro, transmit the statements to
the database machine, and receive their responses in spreadsheet format.
Microsoft Windows is required.
MIC
( 5 )
----- DBC/1012 Model 3, Software Release 3.2, | 01-mAY-90
|C I S| from Teradata | MIC
-----
Additional host-based software from third- party vendors can also manage the
Call Level Interface to the TDP: NOMAD2, FOCUS, PC/SQL-LINK, and INTELLECT.
More connectivity will be announced during the next few months, including
links to AION, METAPHOR, RAMIS, and QMF.
Section: 7 Interface Processors
Interface Processors (IFPs) manage the dialogue between users on a mainframe
and the DBC/1012. Each IFP incorporates a channel interface controller, a
CPU, and two high-speed Ynet interfaces.
As DBC/SQL statements are received, IFP software translates the requests,
dispatches appropriate worksteps, and routes data responses back to their
requestors.
Section: 8 Communication Processors
Communication Processors (COPs) manage the dialogue between departmental or
workstation users and the DBC/1012. Each COP incorporates a LAN adapter, a
CPU, and two high-speed Ynet interfaces. Much like an IFP, a COP receives
DBC/SQL statements, translates the request, dispatches appropriate work steps,
and routes data responses back to the requestors.
A minimum of one COP per department-level processor or workstation is required
for operation. More may be added as required, depending on the number of
hosts to be serviced and their respective traffic volumes.
The COP supports TCP/IP, ISO/OSI, XNS, and SNA networking protocols.
Section: 9 Access Module Processors
Access Module Processors (AMPs) perform database manipulation activities. The
AMP software executes database manipulation work steps, accesses the disks as
appropriate, and prepares the resulting data.
Each AMP is responsible for up to four disk storage units. When a relational
request is received that requires the manipulation of multiple rows, each AMP
receives the request and works asynchronously upon its portion of the
database. All AMPs can thus work concurrently, in parallel, on the same
problem.
MIC
( 6 )
----- DBC/1012 Model 3, Software Release 3.2, | 01-mAY-90
|C I S| from Teradata | MIC
-----
Section: 10 Ynet
Ynet is a tree-structured network of packet-sorting elements. It performs
three functions: it broadcasts work messages from the IFPs or COPs to the
AMPs, manages AMP to AMP communication, and merges data results from AMPs back
to IFPs or COPs.
Section: 11 Database Architecture
DBC/1012 is based on the relational model. All data appears in
two-dimensional tables containing rows and columns. DBC/1012 supports views
that are derived from one or more base tables; views built from more than one
table are read-only. Its DBC/SQL language allows users to retrieve and
manipulate this tabular data in a non-procedural fashion, without iterative
loop processing or step-by-step navigation. Statements can be issued directly
by interactive terminal users or may be embedded within application programs.
DBC/SQL provides null value support and allows a DBA to enter a single range
of valid field values. It contains the standard SQL commands for performing
basic, report-oriented calculations, such as sum, count, etc.
DBC/1012 automatically distributes rows of data across storage units to
maximize performance. If desired, the DBA can control the placement of data
on the storage media by specifying clusters.
Section: 12 Integrity/Security
Redundant hardware and software throughout the DBC/1012 ensure that the system
remains operational in the event of a component failure. System recovery is
highly automated and rarely requires human intervention. In the event of a
disk storage failure, a data fallback option is available to ensure that
critical production data is always available during a component outage.
Many hardware features are designed to protect data as it is stored and
transmitted. The DBC/1012 provides enhanced fault tolerance through advanced
error detection and correction algorithms on both the main memory and cache of
each processor module. It also provides parity protection on all main data
and address paths.
A minimum of two IFPs per host is required for fail-safe operation. More may
be added as required, depending on the number of hosts to be serviced and
their respective traffic volumes.
MIC
( 7 )
----- DBC/1012 Model 3, Software Release 3.2, | 01-mAY-90
|C I S| from Teradata | MIC
-----
DBC/1012 supports a fallback option. When it is specified, a copy of the
prime data of each disk storage unit is distributed evenly across other DSUs.
Should a DSU fail, the DBC/ 1012 automatically directs requests for its data
to the other supporting drives. After the unit is repaired, DBC/1012
automatically re-establishes the primary copy of the data using the fallback
copy, including any changes that have been made while the unit was down. Data
remains consistent and available.
Teradata also supports a permanent journal that records before and after
images of all rows that are changed. Before images can be used to reset
("roll back") data in a table to some prior point in time. After images can
be used, in conjunction with an archived copy of the data, to restore ("roll
forward") a table to its most current state. Because it records only changed
rows, the journal consumes less disk space than the fallback option.
Teradata automatically maintains a Recovery Control Catalog (RCC) for use in
conjunction with the journal. The RCC keeps an audit trail of all archive and
recovery actions (e.g., checkpoints, dumps, restores, rollbacks, and
rollforwards), including which user initiated the action. The information may
be useful in determining the proper sequence of recovery actions for restoring
a given table.
Locks can be applied to databases, tables, and views. When a lock is placed
on a view, DBC/SQL automatically applies the specified lock to each
underlying table.
Section: 13 User Authorization
Teradata's authorization scheme is based on a hierarchical mechanism. One
user, a superuser or DBA, has full rights to all aspects of the system. Other
users and user groups can inherit certain permissions from the main user, and
still more users can inherit certain permissions from that level of
authorization.
Section: 14 System Performance
Outstanding response time can be achieved because of the system's parallel
processing. Simple requests can be satisfied as quickly as with conventional
systems. Complex requests run, according to Teradata, four to 10 times faster
than conventional systems, depending on the number of processors in the
configuration. By distributing the workload over parallel processors, the
DBC/1012 avoids the performance bottleneck that is common in a mainframe CPU.
MIC
( 8 )
----- DBC/1012 Model 3, Software Release 3.2, | 01-mAY-90
|C I S| from Teradata | MIC
-----
Section: 15 Evaluation
Several years ago, Teradata blazed the trail for fault tolerant,
microprocessor-based, parallel processing architecture with its first database
machine. Today, it retains its technological lead and often sells its
expertise to major hardware manufacturers who wish to apply the technology to
more general applications.
Teradata can handle huge volumes of data and provides performance suitable to
online transaction processing. Teradata shows its excellent price/performance
most clearly when it processes complex ad hoc requests on databases that reach
100 to 200 gigabytes (GB). The 6GB of disk storage in its base configuration
exceeds the maximum capacity of many mainframe systems. This combination of
storage capacity and performance is otherwise available almost exclusively on
the largest mainframe systems. Even among manufacturers committed to OLTP
systems, only the highest-end Sequent Symmetry system begins to approach this
capacity.
Section: 16 Cooperative Processing
The Teradata database machine implements an architecture that has come to be
known as cooperative processing. In accord with the definition of cooperative
processing, the machine automatically parses and distributes tasks to the best
processor for the job. With Teradata, end user software (in this case,
residing on a host computer) is clearly separated from back-end database
functions, and the back-end processes are even further differentiated
according to function. While IBM, Digital, Hewlett-Packard, and other
companies are implementing a different division of labor among cooperating
processors, Teradata's is well suited for its specialized purpose and provides
the same benefits, with each microchip performing a specialized task.
Section: 17 Broadening the Product Line
Teradata is now broadening its product line to include interfaces to standard
communication protocols and to UNIX in particular. This move into open
systems architecture follows a trend that Teradata has seen among its current
customers towards open systems and distributed transaction processing.
Teradata has already made software available for a PC or LAN host, also very
much in line with the emerging distributed environment.
Another avenue for development lies in batch processing. Teradata is now
exploring ways to apply parallel processing to batch jobs. The forthcoming
(end 1990) release will include a multiload utility function that will
MIC
( 9 )
----- DBC/1012 Model 3, Software Release 3.2, | 01-mAY-90
|C I S| from Teradata | MIC
-----
transform user-defined batch transactions into instructions for fulfilling the
request using parallel processing.
In addition, Teradata is planning to incorporate optical storage technology
into its product. This strategy is almost a necessity, since optical media
are best suited to mass storage. In fact, optical storage disks replicate
Teradata's uniqueness in bringing mass storage to smaller hosts.
This future puts Teradata in an excellent position for the computer
environment of the l990s. Analysts predict that intelligent workstations will
replace terminals and that processing will shift from the mainframe to the
intelligent workstation. Smaller machines will replace the individual
functions of a large mainframe, and mainframe functions will become more and
more confined to serving as database storage/retrieval units. Most corporate
information systems will operate as a distributed environment accessing a
central store of information.
Teradata should do particularly well in a distributed and cooperative
environment. Here, a dedicated database machine is a practical solution in
more situations than in centralized environments, where a mainframe performs
many functions besides database management.
Section: 18 Weaknesses
While DBC/1012 shows its greatest strength as a back-end system, its greatest
weakness lies in its SQL language. Release 3.0 of DBC/SQL became available in
June 1987 and has not been significantly enhanced since that time. DBC/ SQL
Release 3.2 provides null value support and accepts a single range of valid
field values but does not offer referential integrity, user-defined data
types, or database procedures. DBC/SQL is due for an update.
Section: 19 Conclusions
In conclusion, even though relational DBMs are becoming faster and more
powerful, Teradata should remain in a good competitive position for the
special markets that require its large disk capacity and fast performance.
While new fault tolerant machines are hitting the market in abundance, none
offers Teradata's particular combination of huge disk capacity, scalability,
fault tolerance, and OLTP-level performance. Teradata should serve
distributed and cooperative environments particularly well. Moreover, if
companies continue to move their information systems in this direction,
Teradata should attract new markets and target industries as well.
(c) MIC
MIC
( 10 )
----- DBC/1012 Model 3, Software Release 3.2, | 01-mAY-90
|C I S| from Teradata | MIC
-----
MIC
( 11 )
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 914.1 | | DATABS::DATABS::NEEDLEMAN | today nas/is, tomorrow... | Tue May 07 1991 18:39 | 50 |
| from
Subj: NEWS IN A NUTSHELL - ISSUE 198
TERADATA - To have introduced this week a fourth-generation database
computer based on Intel i486 chips that claims eight times the power
of a conventional mainframe at a fraction of the cost. The DBC/1012
Model 4 offers parallel processing for business applications and
incorporates "parallelized" Structured Query Language that enables
users to access the machine using standard SQL commands. The system
is already installed in customer sites at AT&T, Delta Airlines, and
Bell Industries. It can be configured with six to 1,000 processors,
each with 9 Mips of processing power. Each processor module has
256Kbytes of cache memory and 8Mbytes of RAM. The Model 4 comes
standard with a communications processor that connects it to
Ethernet LANs, and a DBC Manager workstation that simplifies
monitoring and capacity planning. The system also runs under a new
version of Teradata's RDBMS, Release 4.1.2, which enhances support
for transaction processing and provides for more real-time
continuous operation. The Model 4 stores up to 10 Terabytes in
modular cabinets for managing large relational databases. Pricing
starts at $816,000.
The same article also mentions the fact that Teradata's chief
scientist, Philip Neches, has left Teradata to join NCR.
{InformationWeek, 4/22/91}
3Q91 3Q90 Previous Quarter 91
Revenue $64.6m $61.7m $63.8m
Net Income $1.5m $5.2m $0.4m
o With nearly 200 processors shipped to date, the Model 4 has
exceeded Teradata's expectations for both performance and
reliability. Teradata is now into full production of the Model 4
and believes it will provide a significant portion of revenues in
the coming quarters.
o Added more new customers in the third quarter than in the first
and second quarters combined. While European revenues are still
below original expectations, several significant shipments were
made to European customers in the quarter.
o Sold 721 processors in 43 transactions during the third quarter.
18 of these transactions, comprising 246 processors, were
expansions or upgrades of previously installed systems and 25 were
new systems.
o International revenues were 16.4% of total revenues, up from 13.0%
in the second quarter and 6.5% in the first quarter.
{Competitive Information System Business Wire, 4/22/91}
|