Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
eric_ht
Starting Member
37 Posts |
 Posted - 2008-11-18 : 20:06:11
|
| I keep getting this error on various fields in a data flow task: "The value could not be converted because of a potential loss of data". The fields are of the same type and length (char(10)), contain no nulls or invalid characters that I can tell. I change the error output to ignore the failure and it works fine. But I certainly don't understand why the errors being thrown and why it's only choosing select fields to happen on.I tried changing the data types to varchar instead but that did not make a difference.Any help is appreciated.thanks |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-11-18 : 21:46:38
|
| It happens due to datatype mismatch. |
 |
|
|
eric_ht
Starting Member
37 Posts |
Posted - 2008-11-18 : 21:56:54
|
| And that's what it turned out to be, even though the two fields I were mapping were both of the same length and type. But here's what happened:I copied and pasted a data flow task and went into the data flow and changed the stored proc to what the newly created data flow should have and mapped my columns. When I would go into the mappings it shows the two columns being mapped as different types when I moused over the mapping line. So I deleted the ole db source and destination and created from scratch and the mappings show the correct data types.I guess copy and paste is not such a good idea here huh?Thanks for your reply. |
|
|
|
|
|
|
Data Flow Data Mapping Issues...