<div>
This is basically what we thought we had to do, but I was hoping there was a way to set the Data Flow to fail if the input file was not present.<br />
<br />
Thanks.
</div>


This is basically what we thought we had to do, but I was hoping there was a way to set the Data Flow to fail if the input file was not present.

Thanks.

<div>
<div class="content wysiwyg-content">
I have an SSIS package that is a simple dataflow task. I have a mail task off the data flow task as a &quot;failure&quot; task to email me if the dataflow fails. The dataflow consists of a flat-file source to an OLEDB destination. If I delete the input file and run the package the data flow task &quot;fails&quot; but never goes to the mail task. If I open the data flow task the flat-file source is red and that's it. In the Progress window it says the flat-file source component failed in pre-execute. <br />
<br />
Other than adding a step prior to the data flow to check for the file and email if it is missing, is there a way to get the data flow task to fail and just fall through to the failure mail task in the package?
</div>
</div>


I have an SSIS package that is a simple dataflow task. I have a mail task off the data flow task as a "failure" task to email me if the dataflow fails. The dataflow consists of a flat-file source to an OLEDB destination. If I delete the input file and run the package the data flow task "fails" but never goes to the mail task. If I open the data flow task the flat-file source is red and that's it. In the Progress window it says the flat-file source component failed in pre-execute. 

Other than adding a step prior to the data flow to check for the file and email if it is missing, is there a way to get the data flow task to fail and just fall through to the failure mail task in the package?

SSIS - How to handle missing flat file in dataflow task

Microsoft SQL Server is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.SQL Server is available in multiple versions, typically identified by release year, and versions are subdivided into editions to distinguish between product functionality. Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning.