Part 2: Integration Environments
In the first installment of “How To Better Manage Your Test Data In 2017” we covered Pre-Production Data. In part two, we will cover Integration Environments, which typically only require a subset of the Pre-Production Data.
Integration Environments serve several purposes:
- They provide additional security because different business units only access the data that they actually need.
- They are perfect test beds for component and integration tests, which require large amounts of data.
- They allow groups of testers to refresh data independently of the schedule in which the pre-production is refreshed
The best way to create Integration Environments is to use tools that make fast file system level copies of your DB2 objects.
It is common that multiple copies of the same set of tables are stored in the same DB2, for example, one set of tables for each group of testers. Therefore, these tools must allow you to easily select the set of tables that you need, plus they must offer the option to rename those tables during the copy process. Additionally, if no pre-production exists, it must be possible to make consistent in-flight file system level copies directly from the production itself.
UBS-Hainer’s BCV5 makes fast copies of DB2 table spaces and indexes, including structures and data, on file system level. On average, it only requires 10% of the CPU and only 10% elapsed time that an Unload/Load process consumes. Our customers have significantly optimized their test data management processes. We will gladly put you in contact.
For more information check us out on Youtube or contact us directly at: