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 |
|
SergioM
Posting Yak Master
170 Posts |
 Posted - 2012-05-24 : 14:49:02
|
I'm using the SSIS Import wizard & I've chosen my file. It is a non-unicode file. I map it out & when I go to run the package, I see this error.quote:
cannot convert between unicode and non-unicode string data types
I've tried to go back & just click off 'unicode' on it, however if I do that, I get a different error message when I map the fields. So clearly, it is non-unicode & it has to stay that way. How do I get SSIS to process it? |
|
|
yosiasz
Master Smack Fu Yak Hacker
1635 Posts |
Posted - 2012-05-24 : 15:13:52
|
| what is your Data Type properties (in the Input and Output properties tab) is it nvarchar?<><><><><><><><><><><><><><><><><>If you don't have the passion to help people, you have no passion |
 |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2012-05-24 : 16:03:49
|
quote:
Originally posted by SergioM
I'm using the SSIS Import wizard & I've chosen my file. It is a non-unicode file. I map it out & when I go to run the package, I see this error.quote:
cannot convert between unicode and non-unicode string data types
I've tried to go back & just click off 'unicode' on it, however if I do that, I get a different error message when I map the fields. So clearly, it is non-unicode & it has to stay that way. How do I get SSIS to process it?
you can add a dervied column task in between to cast it to non unicode if you're sure it contains non unicode data------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/ |
|
|
|
SergioM
Posting Yak Master
170 Posts |
Posted - 2012-05-25 : 17:19:24
|
quote:
Originally posted by yosiasz
what is your Data Type properties (in the Input and Output properties tab) is it nvarchar?
Hmm, that's odd. I don't know what they were set to before, but this time around I set every column to nvarchar(max) and it imported completely & without errors. Of course I want to go back & remap them properly, but in spite of the error message, it was not related to the unicode/non-unicode file type.It works! Thanks as always! |
|
|
|
|
|
|
|
|
Unicode error message