There are a variety of testing requirements for any data warehouse and database — and especially dual platforms like Teradata — where ETL and BI prototypes, application stress testing, and performance benchmarking are essential.
The value of good test data to DBAs is well known:
“Testing of database-intensive applications has unique challenges that stem from hidden dependencies, subtle differences in data semantics, target database schemes, and implicit business rules.
This article is part of a 4-step series introduced here. Navigation between articles is below.Step 3: Test Data Generation & Provisioning
In prior steps outlined in this series, you have determined the purpose and properties of the data, and who will produce and consume it.
Database and solution architects depend on realistic test data to:help create new databases, prototype ETL jobs or applications benchmark performance in new or existing platforms stress-test systems protect confidential information in existing systems if database work is outsourced or used for demonstrations.
Production data runs the risk of exposing personally identifiable information (PII), proprietary information, or may not reflect the types or volume of real data that can be encountered in the future.
The increasing sophistication of software applications and the expanding role of database testers require high volumes of high quality, realistic test data that can faithfully represent existing, and stress-test new, platforms.