Trouble Importing CSV. "Truncation" despite Varchar(max)

Question

Post reply

Trouble Importing CSV. "Truncation" despite Varchar(max)

homebrew01

SSC Guru

Points: 55549
More actions
February 20, 2013 at 5:04 am

#289881

I'm trying to import a .csv file. One column has text from a website comment filed, so there are all kinds of characters entered. Using the Import Wizard, I set the incoming column length to 8000, and the column in my staging table to varchar(max) or nvarchar(max), but I still get these messages. I removed any commas from the file, but there are ampersands and whatnot in that colum. A warning box sometimes comes up when defining the wizard options, and I choose "ignore" for data truncation, but no effect.
Is there a foolproof way to "import everything" into a SQL table ?
Error 0xc02020a1: Data Flow Task 1: Data conversion failed. The data conversion for
column "Status" returned status value 4 and status text
"Text was truncated or one or more characters had no match in the target code page.".
(SQL Server Import and Export Wizard)
Error 0xc020902a: Data Flow Task 1: The "output column "Status" (14)" failed because truncation occurred,
and the truncation row disposition on "output column "Status" (14)" specifies failure on truncation.
A truncation error occurred on the specified object of the specified component.
Forum Etiquette: How to post Reporting Services problems

[/url]

Forum Etiquette: How to post data/code on a forum to get the best help - by Jeff Moden
[/url]

How to Post Performance Problems - by Gail Shaw
[/url]

mister.magoo SSC-Forever Points: 47174 More actions · Answer 1

Is this a one-off import or are you setting up a repeatable process?

MM

select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);

homebrew01 SSC Guru Points: 55549 More actions · Answer 2

Today it is a one-off. But I will be setting up a weekly process for future imports.

I thought I would use the wizard the first time, then save it as a package for future use.

There are probably some funky characters in the text strings that SQL doesn't like.

EDIT: There were some commas in one of the columns that i removed, and in one text box there was 3 pages of diatribe about the economy that had 8,900 characters. I modifed those, and the import worked, but a cumbersome solution.

mister.magoo SSC-Forever Points: 47174 More actions · Answer 3

Well, if the import file is invalid because it contains unquoted separators in the data, you will always struggle.

You should get the producer of the data to remove invalid characters and/or look at using a more unusual character as a delimiter.

The "pipe" symbol | is quite often used because it doesn't often appear in common language...

MM

select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);

bdloving 4446 SSC Enthusiast Points: 198 More actions · Answer 4

//one or more characters had no match in the target code page//

seems to be wierd characters,

you could try a varbinary field instead of varchar

Trouble Importing CSV. "Truncation" despite Varchar(max)

Cookies on SQLServerCentral