Hello , I am getting a error when I excute my package. The column which is getting tha error has datatype of smallmoney.Can some one check that error message and please help me , its really urgent. [OLE DB Destination [3537]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Unspecified error". [OLE DB Destination [3537]] Error: There was an error with input column "EMPIDRate" (3601) on input "OLE DB Destination Input" (3550). The column status returned was: "The value violated the integrity constraints for the column.". [OLE DB Destination [3537]] Error: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "input "OLE DB Destination Input" (3550)" failed because error code 0xC020907D occurred, and the error row disposition on "input "OLE DB Destination Input" (3550)" specifies failure on error. An error occurred on the specified object of the specified component. There may be error messages posted before this with more information about the failure. Thank you.

is it validation error or runtime error? if runtime error, could you CONFIGURE ERROR OUTPUT on oledb destination and redirect error rows to a flat file destination to find out what rows caused error and let us know the result.http://www.rad.pasfu.com

Try to use data type conversion in the derived column transformation: (DT_CY)[EMPIDRate] for the input column EMPIDRate and check the result. Did the destination column accepting Small money type or not.latha

or you could change the data type of the Source adapter to be nvarchar (DT_WSTR) and then inspect the values in a Data Viewer. is it possible that the data contains a currency symbol that SSIS doesn't like?Todd C - MSCTS SQL Server 2005 - Please mark posts as answered where appropriate.

I suspect you got bad data, please do what Reza said and you must be able to see at what record # you have the culprit. To avoid failing next time I recommend you examine the constrains on the DB side and add some cleansing to your package in form of the very error row redirection mentioned above.Arthur My Blog

Thank you all for your ideas. I have changed my table structure and added a column ID int IDENTITY (1,1). As there are some duplication values coming up on my primary key columns, so I added the column IDENTITY and now my package is running. Thank you all.This MSDN is awesum form.