I am planning on using a File Watcher task to have an SSIS wait until a file is submitted. This seems to work ok. However I want the package to launch itself again once it completes, or schedule itself to launch again in a couple of minutes. That way I could
relaunch the task after it has processed and moved the current set of files. That way it would process loads more or less as they are exported by the source systems. I'm not even sure how to approach this problem as its not something I've done with SSIS in
the past. The current solution uses batch files and DTEXEC so I'm guessing its scheduling via the windows scheduler. I would lean towards SQL Server Agent personally but that's just because I'm looking for something that will expose what jobs are running to
me more easily than investigating processes.
I also wanted to know if it was possible to see what other packages were already running. That way if a package inadvertently launched while another instance of itself was still processing it could just shut itself down. I may also have dependencies between
packages. So if package A was running, package B should wait rather than processing any of its files, and vice versa. I could do this by logging the packages in and out of a cusotm locks table, but that feels unweildy and the package may crash
out and not "unlock" cor
View Complete Post