Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Programming / SQL / July 2008

Tip: Looking for answers? Try searching our database.

SSIS & Code pages

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Bob McClellan - 24 Jul 2008 18:01 GMT
Sorry for the cross post.  I originally posted this in the wrong NG.

I've been working on setting up a package to simply append data into a table
residing in a 2005 db.
(I've even tried importing the flat file from management studio)

I continue to get this error, regardless of how I structure the target
table.
 [Flat File Source [1]] Error: Data conversion failed. The data conversion
for column "first_name" returned status
 value 4 and status text "Text was truncated or one or more characters had
no match in the target code page.".

I feel the problem is in the "no match in the target code page"

If I go to an old box running SQL Server7, it imports with no problem.

Any advice on how to combat this would be very much appreciated.
Thanks in advance,
bob.
Aaron Bertrand [SQL Server MVP] - 24 Jul 2008 18:05 GMT
How can you be sure that the truncate part of the message is not the
problem?

Anyway, is the destination column varchar or nvarchar?  What is the
collation of the database, and the collation of the column?  Have you tried
identifying the data that is causing the problem (e.g. break the file into
smaller and smaller chunks until you have some that fail and some that
don't, which should help narrow down which pieces of data are being
rejected)?

On 7/24/08 1:01 PM, in article eyRTM7a7IHA.4468@TK2MSFTNGP02.phx.gbl, "Bob
McClellan" <bobmcc777@gmail.com> wrote:

> Sorry for the cross post.  I originally posted this in the wrong NG.
>
[quoted text clipped - 16 lines]
> Thanks in advance,
> bob.
Bob McClellan - 24 Jul 2008 19:42 GMT
Aaron,

> Have you tried
> identifying the data that is causing the problem (e.g. break the file into
> smaller and smaller chunks until you have some that fail and some that
> don't, which should help narrow down which pieces of data are being
> rejected)?

Thanks for this suggestion.  I was so caught up in thinking I had a
coallition
problem that I went right past the obvious.
I had 55 columns in the target table.  I commented them all out in my sql
and
started using process of elimination with each column.  I had a few problems
that needed to be converted and this allowed me to append to the 2005 db.

Thanks again Aaron,
..bob
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.