Hopefully Last queation
I would recommend using the File Properties Task from CodePlex. It functions similarly to the File Watcher - except the file can already be present (it looks at "state" rather than "actions"), and it has a timeout. You could use two tasks - one looking for the "success" file, one looking for the "fail" file - inside a For Loop that executes until one of the files is found. Use a several second timeout on each task so you don't unnecessarily consume CPU. Talk to me now on
December 21st, 2011 8:30pm

in a script task, is it possible to set a different task to fail whilst it is executingDont ask me .. i dont know
Free Windows Admin Tool Kit Click here and download it now
December 23rd, 2011 11:51am

No. But you can abort the package or set some variable(s) to cause a task down the pipe line to fail or to not to execute. You know, the most elegant approach to branch your package execution conditionally using Precedence Constraints. See an example: http://www.simple-talk.com/sql/ssis/working-with-precedence-constraints-in-sql-server-integration-services/ Arthur My Blog
December 23rd, 2011 12:03pm

I would recommend using the File Properties Task from CodePlex. It functions similarly to the File Watcher - except the file can already be present (it looks at "state" rather than "actions"), and it has a timeout. You could use two tasks - one looking for the "success" file, one looking for the "fail" file - inside a For Loop that executes until one of the files is found. Use a several second timeout on each task so you don't unnecessarily consume CPU. Talk to me now on
Free Windows Admin Tool Kit Click here and download it now
December 23rd, 2011 12:43pm

I have looked at your suggestion, but dont know how I can impliment it in this case, I have a for loop which takes data from various SQL tables and creates a flat file. A different system, uses the data within that file and creates a new file for updating the tables.This is wher the trouble begins I am using a file watcher task ( http://www.sqlis.com/post/file-watcher-task.aspx ), which watches a directory for the return file. this task has a timeout parameter. The length of time that it takes to generate the return file varies so I have to set an umlimited time. This then stops me from being able to contuine if the file is not created. also I need to be able to manualy fail this task if adifferent file appears in the directory. I was hoping that I could put a second file watcher from the for loop and if it finds a certian file, then fail the 1st file watcher task. I have no idea how i can set this section of the package up so that once the for loop has finished and created the output file, i can 'suspend' the package until either the new input flatfile is found, or fail it if a different flatfile is found, any ideas?Dont ask me .. i dont know
December 23rd, 2011 12:45pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics