Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
We set up tasks for the real-time refresh and also build historical data in the target.
If we select not to truncate the table (do nothing) on a task because of maintaining historical data in the target table that are getting purged in the source, we will never be able to choose the reload to fix a mismatch, or in some other cases or issues, the reload is an easier fix. Besides us, does anybody else follow a similar task design to prevent data from getting deleted from the source and not have an option to reload if needed? I like to hear from others.
Thanks,
AU
Hi Alan,
The only solution that would be possible is to backup data instead of the table and then after reloading, restore data to the current table because of reports running against the table.
Thanks
Hi AU,
I think with your use case then that will be the best approach. Good luck! You can always open a support case if you need further assistance
Thanks
Lyka