cannot convert between unicode and non-unicode

Question

cannot convert between unicode and non-unicode

Mark Minneman

SSC Enthusiast

Points: 108
More actions
May 21, 2009 at 12:06 pm

#134363

I have an SSIS package with a Data Flow Task which contains an OLE DB Source and an OLE DB Destination.
The OLE DB Source is a SQL Command which contains a giant SELECT statement from a SQL Server 2005 database. The field referenced by the "cannot convert between unicode and non-unicode" error is a CHAR.
The OLE DB Destination is a different SQL Server 2005 database. The corresponding field in the destination database is a VARCHAR. I get the same "cannot convert between unicode and non-unicode" error on this object, as well.
Can someone shed some light on where unicode comes into play in a CHAR => VARCHAR conversion and how to resolve/prevent this? I read through some of the other forum posts regarding this error and none seemed to apply.
Thanks in advance!!

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Mark Minneman SSC Enthusiast Points: 108 More actions · Answer 1

Please disregard this question. With a little more digging, I found a nugget suggesting use of Advanced Editor. By going into Input and Output Properties, I was able to explicitly change the data type of the internal output column of the offending field. I don't know why the original package author had specified the output column as unicode!

le_billy Old Hand Points: 312 More actions · Answer 2

Hi Mark,

I am a super newbies and try the same import as you and I am getting the same error, can you be specific as to how you get to the advance option, I have look around and could not find it.

Thank you

Billy

Mark Minneman SSC Enthusiast Points: 108 More actions · Answer 3

Instead of double-clicking on the object to edit the basic properties, right-click on it and select Advanced Editor.

le_billy Old Hand Points: 312 More actions · Answer 4

le_billy

Old Hand

Points: 312

July 8, 2010 at 7:46 pm

#1190579

😀 thank you Mark, you made my day.

rmairy SSC Enthusiast Points: 180 More actions · Answer 5

hi dudes!

i came across with the same error.

The solution which i found was to create a package through import/export wizard ( it will create an extra data conversion DATA FLOW TRASNFORMATION) which will automatically convert between unicode and non unicode.

Let me know if you need more explanation.:-)