15.00 - OLTP - Teradata Database

Teradata Database Design

prodname
Teradata Database
vrm_release
15.00
category
User Guide
featnum
B035-1094-015K

OLTP

Consider the following simple example: A customer, Mr. Brown, orders a calendar. The graphic diagrams the actions taken against the database.

The transaction flow is outlined in the following process stages:

1 A new order, 7326, is opened on the Order table.

2 The remaining columns for the order are filled out, including the Customer number for Mr. Brown, 3, and the date the order was placed, April 5.

3 A new shipping order, with order number 7326 and item number 3509, is opened on the Order Item Shipped table.

4 The remaining columns for the shipper are filled out, including the quantity shipped, 1, and the date the order was shipped, April 5.

5 The transaction is complete.

Three key aspects of this transaction deserve your attention:

  • Only a few of many possible tables were accessed.
  • None of the accessed tables, some of which might have billions of rows, were scanned.
  • Very little I/O processing was required to complete the transaction.
  • These three attributes are characteristic of all OLTP environments. The requirements are simple and involve only a quick-in, quick-out approach to the database. Most modern relational database engines are designed specifically for maximum efficiency with these kinds of workloads.