• No, it's SQL 2005 SSIS and importing a flat file. The file sometimes has bad rows such as missing columns or bad characters. I have a flat file connection specified for the file that I import so if it fails that, I want that record exported out and to continue on the import.

    On the other side of the import, if the import into the table fails, I want to see the row it fails by writing out to another file and continuing on the import.

    This also allows me to just import the affected row once it's fixed so I don't have to re-import the full file since it's quite large