peterzeke (7/26/2013)
Thanks for such a quick reply, Phil.As you suggested, I exported a spreadsheet as a text file. The values in the text file match the values in the spreadsheet (i.e., 10.4 in Excel exported as 10.4 in the text file), but the decimal data loaded via SSIS ends up wacky in the sql destination table.
6.4 loaded as 6.4000000000000004
5.8 loaded as 5.7999999999999998
0.58 loaded as 0.57999999999999996
0.8 loaded as 0.80000000000000004
but
10.1 loaded as 10.1
4 loaded as 4.
The SQL destination column is nvarchar since any column of data in excel might have a text value rather than a numeric/decimal value. We have data entry validation rules applied to the spreadsheet, specifically regarding min/max decimal values, but, once in a while a text value needs to be entered and therefore the data validation is removed for that specific cell.
OK - can you also confirm that the datatype of the column in the SSIS pipeline is varchar(n)?
If so, can you put a data viewer somewhere in the data flow to check whether the value has already changed by the time it comes into SSIS?
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.