May 20, 2013 at 1:57 am
I was importing a table data from excel sheet using SSIE wizard. After mapping the table its giving error
Operation stopped...
- Initializing Data Flow Task (Success)
- Initializing Connections (Success)
- Setting SQL Command (Success)
- Setting Source Connection (Success)
- Setting Destination Connection (Success)
- Validating (Error)
Messages
* Error 0xc02020f6: Data Flow Task: Column "title" cannot convert between unicode and non-unicode string data types.
(SQL Server Import and Export Wizard)
* Error 0xc02020f6: Data Flow Task: Column "objectiveIndication" cannot convert between unicode and non-unicode string data types.
(SQL Server Import and Export Wizard)
* Error 0xc004706b: Data Flow Task: "component "Destination - Protocol" (104)" failed validation and returned validation status "VS_ISBROKEN".
(SQL Server Import and Export Wizard)
* Error 0xc004700c: Data Flow Task: One or more component failed validation.
(SQL Server Import and Export Wizard)
* Error 0xc0024107: Data Flow Task: There were errors during task validation.
(SQL Server Import and Export Wizard)
Anybody help me out on this.
Thanks in advance
May 20, 2013 at 1:59 am
Your data comes in from Excel as Unicode.
If you are mapping it straight to varchar() columns, you will get an error.
Add a data conversion component to convert your columns from Unicode and then map the converted columns.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
May 21, 2013 at 10:22 am
You can import into the NVARCHAR datatype from excel or use data conversion task is ssis
May 22, 2013 at 7:22 pm
To resolve the issue you can follow either of the two steps:
1. Change your column data type in SQL Server table to Varchar
2. If you do not want to change the data type develop a SSIS package and add a step to convert the data from NVARCHAR to VARCHAR before inserting it into SQL table. You can refer the below post for a step wise process to do this.
SSIS: 3 Ways to resolve Unicode and non-unicode data type issue?
http://www.sqlservercentral.com/Forums/Topic906852-391-1.aspx
Vikash Kumar Singh || www.singhvikash.in
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply