SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 General SQL Server Forums
 New to SQL Server Programming
 Import data Problem
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

montecarlo2079
Starting Member

20 Posts

Posted - 01/16/2013 :  08:28:50  Show Profile  Reply with Quote
When I import a text file and have it create its own table, the import and table creation work just fine.

When I create a table myself and define the fields, and then try to import the data Im getting all sorts of errors.

Messages
Error 0xc02020f4: Data Flow Task 1: The column "State Fiscal Year To Date of Service" cannot be processed because more than one code page (65001 and 1252) are specified for it.
(SQL Server Import and Export Wizard)

Error 0xc02020f4: Data Flow Task 1: The column "Claim Type Code" cannot be processed because more than one code page (65001 and 1252) are specified for it.
(SQL Server Import and Export Wizard)

Error 0xc02020f4: Data Flow Task 1: The column "Detail Line Number" cannot be processed because more than one code page (65001 and 1252) are specified for it.
(SQL Server Import and Export Wizard)

Error 0xc004706b: Data Flow Task 1: "Destination - IPDETAILAP" failed validation and returned validation status "VS_ISBROKEN".
(SQL Server Import and Export Wizard)

Error 0xc004700c: Data Flow Task 1: One or more component failed validation.
(SQL Server Import and Export Wizard)

Error 0xc0024107: Data Flow Task 1: There were errors during task validation.
(SQL Server Import and Export Wizard)


Any IDea what might be wrong?

James K
Flowing Fount of Yak Knowledge

3744 Posts

Posted - 01/16/2013 :  10:21:08  Show Profile  Reply with Quote
Do the two tables - the table created by SSIS and the table you manually created - have the same columns with the same data types? I suspect something like varchar in one case and nvarchar in another case. You can script the tables from object explorer and compare. Or, for debugging purposes, import the data twice - first time letting SSIS create a new table, and then a second time, truncate that table and import again into that same table. That surely should succeed, one would think.
Go to Top of Page

visakh16
Very Important crosS Applying yaK Herder

India
52325 Posts

Posted - 01/16/2013 :  22:38:36  Show Profile  Reply with Quote
FYIO 65001 is windows codepage for UTF-8

what you could do is open your package in BIDS and add a dervied column task in between source and destination in data flow and convert those unicode to non unicode or vice versa

------------------------------------------------------------------------------------------------------
SQL Server MVP
http://visakhm.blogspot.com/

Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.06 seconds. Powered By: Snitz Forums 2000