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.

 All Forums
 General SQL Server Forums
 Data Corruption Issues
 Import Excel Data error

Author  Topic 

vbx
Starting Member

38 Posts

Posted - 2007-10-22 : 11:56:59
I am using the import Wizzard in SQL Server 2005 for the first time and trying to import some excel data into the db table.

I keep getting this error. Any ideas??

- Validating (Error)
Messages
Error 0xc02020f6: Data Flow Task: Column "game_ID" cannot convert between unicode and non-unicode string data types.
(SQL Server Import and Export Wizard)

Error 0xc004706b: Data Flow Task: "component "Destination - cfb_boxscores" (137)" 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)

blindman
Master Smack Fu Yak Hacker

2365 Posts

Posted - 2007-10-22 : 21:30:36
I'm guessing that your destination column as a unicode datatype (NVarchar, NChar, ...), which has an expanded character set compared to non-unicode datatypes (Varchar, Char, ...).

There should be a property setting in your SSIS package for your datasource columns where you can specify whether to treat it as Unicode or Non-unicode.

Also, rule of thumb: Don't import directly into production tables, even using DTS or SSIS. Import into a staging table with generic datatypes, no indexes, no constraints, etc. Then use a sproc to cleans and verify the data before copying it to your production tables.
If your staging table is generic, you will almost never get errors when loading the data, and any errors when processing the data are much easier to locate and resolve.

e4 d5 xd5 Nf6
Go to Top of Page

ankursharma
Starting Member

1 Post

Posted - 2008-06-13 : 15:05:57
you may use varchar in the table defination at the destination instead of nvarcha and your problem will be solved ;) immidiately.
Go to Top of Page

blindman
Master Smack Fu Yak Hacker

2365 Posts

Posted - 2008-06-13 : 16:32:56
Since the thread is six months old, "immidiately" is probably not soon enough for him.

e4 d5 xd5 Nf6
Go to Top of Page

tosscrosby
Aged Yak Warrior

676 Posts

Posted - 2008-06-13 : 16:52:14
I believe I've seen ankursharma around on other sites. "immidiately" begins reviving OLD threads, responding with the same answers already posted. Maybe to increase post totals "immidiately"???

Terry
Go to Top of Page
   

- Advertisement -