I have a job which reads from a sequential file, trims data in a transformer, and then loads into a table (SQL Server 2005)
There are some columns in the target table which are designated as float and are displaying curious behaviour.
Source Value -- 000004876274.70
Target Value -- 4876274.5
Source Value -- 0006.0300
Target Value -- 6.03000020980835
This behaviour is not restricted to a single column, and till now I have tried following approaches to correct this anomaly,
- read data as varchar and then convert it to decimal and then to float and then insert it.
read it as float and insert it as float