Home Forums Data Warehousing Integration Services here was an error with output column on output "OLE DB Source Output The column status returned was: "The value could not be converted because of a potential loss of data." RE: here was an error with output column on output "OLE DB Source Output The column status returned was: "The value could not be converted because of a potential loss of data."

  • Phillip.Putzback (10/18/2013)


    I have stored procedure that creates a dynamic SQL command to run another stored procedure that has a column INV_STATUS.

    In the internal procedure I cast that column as Numeric, I've tried leaving as INT because that is what the source is and I've tried casting it as varchar

    In my Wrapper procedure I created a Contract so SSIS can pickup the METADATA and have tried all three data type, with the last being the numeric.

    ,[INV_STATUS]=CAST(NULL AS NUMERIC)

    When I run the procedure in SSMS I see the value 6 in every row, when I preview it in the OLE Source in SSIS I see a 6 in every row when I copy the data from SSMS results into excel I see the 6, but when I run it in SSIS I get a 0 in my data viewer when mapping the errors to a row counter.

    Error Code -1071607694

    Error Column - 431

    Error Desc - The data value cannot be converted for reasons other than sign mismatch or data overflow.

    The column 431 in the Advanced editor shows as numeric also.

    The real odd thing is this worked the other day with 12 years of data

    Today I can run it for a month.

    Please explain a couple things,

    Frist - In my Wrapper procedure I created a Contract so SSIS can pickup the METADATA - SSIS is going to be looking at source columns and getting metadata from there. How are you implementing a "contract"?

    Second - what are you running in your OLE Src component? is it the dynamic procedure coded as "Exec dbo.myproc" ?

    Also what are you "previewing" in the OLE Src and how does that differ between design time and run time?