Home Forums Data Warehousing Integration Services Lookup no-match output runs even when there is no no-match output RE: Lookup no-match output runs even when there is no no-match output

  • I believe it will still create it anyway.

    If the empty file is such a problem, you can always delete it right after the data flow. Add a row count component between the lookup and the flat file destination.

    This stores the result into a variable. After the data flow, add a precedence constraint with the expression @RowCount > 0 to a file system task which will delete the file.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP