December 28, 2018 at 10:49 am
Getting this error all the time (importing .csv into SQL Server table). attached pdf shows error.
I already tried a lot of things. Changing code page everywhere, redoing entire solution with different code page,
Setting AlwaysUseDefaultCodePage to =true, and even editing the .dtsx file in text editor manually replacing all 1252 with 65001 and vice versa so that i
t is single code page in dtsx…
Nothing helps. ☹
SQL Server 2016, ssis 2016, SSDT 2015.
Do you have ideas what else i possibly can do ?
ATTACHED PDF. simple data flow task : flat file (csv) to append to existing TABLE in sql server.
i do everything like i usually do and everything works, this particular project this error:
[OLE DB Destination [67]] Error: The column "Student_First_Name" cannot be processed because more than one code page (65001 and 1252) are specified for it.
Likes to play Chess
December 28, 2018 at 10:58 am
VoldemarG - Friday, December 28, 2018 10:49 AMGetting this error all the time (importing .csv into SQL Server table). attached pdf shows error.
I already tried a lot of things. Changing code page everywhere, redoing entire solution with different code page,
Setting AlwaysUseDefaultCodePage to =true, and even editing the .dtsx file in text editor manually replacing all 1252 with 65001 and vice versa so that i
t is single code page in dtsx…
Nothing helps. ☹
SQL Server 2016, ssis 2016, SSDT 2015.Do you have ideas what else i possibly can do ?
ATTACHED PDF. simple data flow task : flat file (csv) to append to existing TABLE in sql server.
i do everything like i usually do and everything works, this particular project this error:
[OLE DB Destination [67]] Error: The column "Student_First_Name" cannot be processed because more than one code page (65001 and 1252) are specified for it.
What is the data type of your destination column?
December 28, 2018 at 11:14 am
All datatypes are Varchar(50), direct load from CSV file, no fancies in the design, data will be picked up further and this stage table this All-varchar-table will be deleted until next load. 3 types of data coming in but we need them all varchars, the longest field is 50 characters.
all INPUT OUTPUT fields in OLED Destination (advanced editor) are DT_STR 50.
Tried converting to unicode. same errors. for EACH field..
Likes to play Chess
December 28, 2018 at 11:21 am
VoldemarG - Friday, December 28, 2018 11:14 AMAll datatypes are Varchar(50), direct load from CSV file, no fancies in the design, data will be picked up further and this stage table this All-varchar-table will be deleted until next load. 3 types of data coming in but we need them all varchars, the longest field is 50 characters.
all INPUT OUTPUT fields in OLED Destination (advanced editor) are DT_STR 50.
Tried converting to unicode. same errors. for EACH field..
Try putting a data conversion between source and destination for student_first_name (convert to DT_STR 50) and mapping the converted column to the destination. Does the error persist?
December 28, 2018 at 3:07 pm
I changed all types via COnversion task from DT_STR to WDT_STR unicode. as on the attached pic.
then i got oledb destination error: cannot convert between non-unicode and unicode data..
when i changed back to original , but still data conversion task there, i again got the CODE PAGE ERROR... 🙁
Likes to play Chess
December 28, 2018 at 4:00 pm
Phil Parkin - Friday, December 28, 2018 11:21 AMVoldemarG - Friday, December 28, 2018 11:14 AMAll datatypes are Varchar(50), direct load from CSV file, no fancies in the design, data will be picked up further and this stage table this All-varchar-table will be deleted until next load. 3 types of data coming in but we need them all varchars, the longest field is 50 characters.
all INPUT OUTPUT fields in OLED Destination (advanced editor) are DT_STR 50.
Tried converting to unicode. same errors. for EACH field..Try putting a data conversion between source and destination for student_first_name (convert to DT_STR 50) and mapping the converted column to the destination. Does the error persist?
Likes to play Chess
December 28, 2018 at 4:01 pm
VoldemarG - Friday, December 28, 2018 4:00 PMPhil Parkin - Friday, December 28, 2018 11:21 AMVoldemarG - Friday, December 28, 2018 11:14 AMAll datatypes are Varchar(50), direct load from CSV file, no fancies in the design, data will be picked up further and this stage table this All-varchar-table will be deleted until next load. 3 types of data coming in but we need them all varchars, the longest field is 50 characters.
all INPUT OUTPUT fields in OLED Destination (advanced editor) are DT_STR 50.
Tried converting to unicode. same errors. for EACH field..Try putting a data conversion between source and destination for student_first_name (convert to DT_STR 50) and mapping the converted column to the destination. Does the error persist?
YES!
it works now , and i also changed code page EVERYWHERE from 1251 to
Likes to play Chess
December 28, 2018 at 4:04 pm
i did what you said, and 1252 to 65001 everywhere, and ALwaysUseDefaultCodePage=true in destination.
But i really don't know why it worked :). i thought i tried the same before.
May be the fact that i re-did the whole project as well it helped. because i messed with the .DTSX 's XML before...
THANK YOU FOR ALL YOUR HELP !
Likes to play Chess
Viewing 8 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply