Hi,
I am building a fact build to hold historical rejects, on top of an existing Data Manager reject table, which gets dropped and created each time the load runs. What is the best way to do this? Also, what is the way to check for a table existence and then run the Fact build? Add a SQL node for checking existence of the reject table and then run the build?
Thanks,
Quote from: avi25ge on 04 Dec 2016 12:28:06 PM
Hi,
I am building a fact build to hold historical rejects, on top of an existing Data Manager reject table, which gets dropped and created each time the load runs. What is the best way to do this? Also, what is the way to check for a table existence and then run the Fact build? Add a SQL node for checking existence of the reject table and then run the build?
Thanks,
Hi,
Is the problem just detecting the existence of the table, or do you need some way of knowing when the build populating that table is complete? If the former, you could use a SQL node in a jobstream to test for the existence of the table. If the latter, you'd probably need to have your build set a flag and look for this to exist.
Cheers!
MF.