August 31, 2017 at 12:00 am
Comments posted to this topic are about the item SSIS as an Execution Engine for Multiple Sql scripts
August 31, 2017 at 1:53 pm
I deleted this, my apologies.
412-977-3526 call/text
August 31, 2017 at 3:41 pm
Yes, I believe this is in the article...
August 31, 2017 at 3:43 pm
Would a driver table of script names with additional attributes such as execution group, order, focus/context, and active/enabled status leverage this? The main SSIS module could just load the script names from there and organize the script runs by the attributes - then you wouldn't have to delete them or rename them or any such hand-work annoyances?
August 31, 2017 at 3:47 pm
Of course you would still have to keep the files tidy. Can they be stuck in a CLOB column-after testing-in the driver table for each and loaded on the fly? This worked really well for me in an Oracle implementation.
August 31, 2017 at 4:41 pm
Yes, that certainly could be done. But we thought it would be an overkill. The log tables keep track of all scripts that were executed. That was enough for us.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply