Note: This is an old article. However, these tips may still apply to newer versions.
Sometimes, an old system is retired that contains data that you wish to keep. The Guard feature of TX enables you to keep data in the staging database when the source system is no longer operational while skipping the regular execution of the old tables. This way, you can keep data from an old system in the data warehouse while appending data from the replacement system.
Step by step
To enable the guard feature on a table, do as follows:
- Right click the table from the old system in the staging area. Choose Advanced -> Guard.
- In the dialogue, there are two checkboxes:
- Guard on deployment: TX will skip the table during deployment, leaving whatever is already there.
- Guard on execution: TX will skip the table during execution.
Make sure to keep a backup of the tables from the old system in a safe location so you can re-establish the data if you need to do a full deployment on a new empty database sometime in the future.
This article applies to: timeXtender 4.5, tX2012, TX2014. Last updated: 2014-03-28.
Regarding the Guard feature - how does this work with project migration between DEV-TEST-PROD environments? I doubt these (multiple) tables are transferred with their critical data intact between environments, which could mean this is a manually handled transfer, with manual reinsertion of data from multiple tables into the migrated project. Hopefully I'm overlooking something obvious and this is a known situation and handled automatically during environment migration.