MSSQLTips

MSSQLTips.com - your daily source for SQL Server tips

Welcome to MSSQLTips Sign in | Join | Help

MSSQLTips » Tip Forums » Tip Discussions » Importing Excel data using SSIS and dealing with unicode and non-unicode data issues

Importing Excel data using SSIS and dealing with unicode and non-unicode data issues

Last post 08-29-2008 1:19 PM by cincydba. 2 replies.

Page 1 of 1 (3 items)
	Sort Posts: Previous Next

12-14-2007 2:24 AM

admin
Joined on 10-08-2007
Posts 676

Importing Excel data using SSIS and dealing with unicode and non-unicode data issues

Reply Contact

This post is related to this tip: Importing Excel data using SSIS and dealing with unicode and non-unicode data issues

http://www.mssqltips.com/tip.asp?tip=1393

Filed under: SQL Server 2005 Integration Services, unicode, Excel exports, Excel imports, non-unicode

05-13-2008 4:22 AM In reply to

dolfa
Joined on 05-13-2008
Posts 1

Re: Importing Excel data using SSIS and dealing with unicode and non-unicode data issues

Reply Contact

I read your tip, looks like very useful. But I am currently fighting with code page issues. I have a dbf file that I suspect been in different codepage than my database. Source connection cannot catch codepage, so I set AlwaysUseDefaultCodepage to True and set Codepage (I found this somewhere), added Data conversion and set codepage of the destination. But I am rewarded only with error, that conversion from source code page (852) to destination (1250 - czech btw) is not supported. Do you have tip somewhere how to solve this?

I am completely lost, I tried various approaches, searched tons of articles, still no luck :(

Thanks for any ideas

Filed under: ssis convert codepage

08-29-2008 1:19 PM In reply to

cincydba
Joined on 08-29-2008
Posts 1

Re: Importing Excel data using SSIS and dealing with unicode and non-unicode data issues

Reply Contact

Your solution didn't work. I still have a column coming in with 90% NULLs.

Page 1 of 1 (3 items)