Teradata Parallel Data Pump

Chapter 2: Using Teradata TPump
Estimating Space Requirements
IGNORE EXTRA ROWS;
INSERT INTO TBL14TA VALUES (:ABYTEINT,:ASMALLINT,:AINTEGER,:ADECIMAL,
:ACHAR,:ABYTE,:AFLOAT,:ADATE);
.DML LABEL LABELB IGNORE DUPLICATE ROWS IGNORE MISSING ROWS
IGNORE EXTRA ROWS;
INSERT INTO TBL14TB VALUES (:ABYTEINT,:ASMALLINT,:AINTEGER,:ADECIMAL,
:ACHAR,:ABYTE,:AFLOAT,:ADATE);
.IMPORT INFILE ./tlnt014.dat
LAYOUT LAY1A FROM 1 FOR 400
APPLY LABELA WHERE ATEST = 1
APPLY LABELB WHERE ATEST = 2;
.END LOAD;
.LOGOFF;
From this script the space requirements can be calculated to be:
• 200 bytes for initialization +
• 200 bytes * 6 for support environment statements +
• 200 bytes * 2 for DML SQL statements +
• 400 bytes for the BEGIN/END load pair +
• 200 bytes for the IMPORT
which is a starting total of 2400 bytes.
Further, assume that Teradata Database can accept about 32 statements per second and that
the load takes a little more than an hour to complete.
The space for partial and complete checkpoints is calculated with the following steps:
Calculating the Space for Checkpoints
1 32 statements per second translates to 1920 statements per minute.
2 1920 / 20 (the packing factor) = 93 partial checkpoints/minute
3 Multiply by 15 (15 minute CP frequency) = 1395 partial checkpoint rows maximum.
4 Each checkpoint row is 117 + (12 * 20) = 357 bytes so 498,015 bytes are in partial
checkpoint rows.
5 Given that the load takes just more than an hour, assume 5 checkpoints are written at
300 bytes each.
Now we have the grand total of space in the log table:
2,400 + 498,015 + 1,500 = 517,980 bytes.
Teradata Parallel Data Pump Reference 87