Teradata® TPump is a data loading utility that helps maintain (update, delete, insert, and atomic upsert) the data in the database. Teradata TPump allows near-real time data to be achieved in the data warehouse.
Teradata TPump uses standard Teradata SQL to achieve moderate to high data loading rates to the database. Multiple sessions and multistatement requests are typically used to increase throughput.
Teradata TPump provides an alternative to Teradata MultiLoad for the low volume batch maintenance of large databases under control of a Teradata system. Instead of updating databases overnight, or in batches throughout the day, Teradata TPump updates information in real time, acquiring data from the client system with low processor utilization. It does this through a continuous feed of data into the data warehouse, rather than through traditional batch updates. Continuous updates result in more accurate, timely data.
Unlike most load utilities, Teradata TPump uses row hash locks rather than table level locks. This allows queries to be run while Teradata TPump is running. This also means that Teradata TPump can be stopped instantaneously.
Teradata TPump provides a dynamic throttling feature that enables it to run “all out” during batch windows, but within limits when it may impact other business uses of Vantage. Operators can specify the number of statements run per minute, or may alter throttling minute-by-minute, if necessary.
- Simple, hassle-free setup – does not require staging of data, intermediary files, or special hardware.
- Efficient, time-saving operation – jobs can continue running in spite of database restarts, dirty data, and network slowdowns. Jobs restart without intervention.
- Flexible data management – accepts an infinite variety of data forms from an infinite number of data sources, including direct feeds from other databases. Teradata TPump is also able to transform that data on the fly before sending it to the database. SQL statements and conditional logic are usable within the utilities, making it unnecessary to write wrapper jobs around the utilities.