Hello,

I am using SSIS to import flat files data into SQL Server 2005.
At the last stage of the pipeline - the SQL Server Destination module, if
the currently inserted record key already exists, primary key costraint
occurs and the *whole data import is rolled back*.

Is there a way to tell SQL Server Destination module that only the
constraint violating record should be rejected and not to force a complete
role back of the entire row set?

A similar situation with foreign key constraint, forced me to rum a lookup
transformation step before reaching the destination, in order to avoid a
foreign key violation situation.

Thanks
Amnon