November 9, 2011 at 8:21 am
Hi All,
I have a package which takes data and convert into .csv file.
Our customer wants the .csv file in UTF-8 format.
Can you pls guide me on this ? Where and what to change.?
Thanks in advance.
Smith.
November 9, 2011 at 11:59 pm
In the Flat File connection manager, you can set the code page to UTF-8.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
November 10, 2011 at 12:50 am
Koen Verbeeck (11/9/2011)
In the Flat File connection manager, you can set the code page to UTF-8.
Thanks a lot for the response. Was trying with it.
2 more doubts.
1. What's that "Unicode" checkbox for.?
2. If I change code page to UTF-8, Do I need to change the data type for each and every output column in advance editor or anywhere else.? Pls guide.
Thanks again.
November 10, 2011 at 1:52 am
Joy Smith San (11/10/2011)
1. What's that "Unicode" checkbox for.?
To convert the strings to unicode strings.
In SQL Server, this is varchar versus nvarchar. Unicode can handle much more special characters than normal code pages. Unicode does take up more space, as it needs more bytes for encoding.
More info:
http://en.wikipedia.org/wiki/Unicode
Joy Smith San (11/10/2011)
2. If I change code page to UTF-8, Do I need to change the data type for each and every output column in advance editor or anywhere else.? Pls guide.
I don't believe so. UTF-8 is an encoding of the text file, it has nothing to do with SSIS itself.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
November 10, 2011 at 2:29 am
Thank you. I will try but just selecting UTF-8 and not changing the data type of any field.
Wel, regarding Unicode. I am aware about unicode datatype. Think my question was not clear. Actualy I wanted to ask, "Unicode" has nothing to to do with UTF-8 format.? If we 'check' unicode check box, then we are not able to select any partiicular format.
Thanks a lot and I think am more clear now. Will try one by one and see.
November 10, 2011 at 2:55 am
Ah well, your question is indeed more clear now
If you have "regular" strings, aka non-unicode, you need to specify a code page that describes how the characters needs to be encoded. In the Western world, this is usually 1252 (ANSI - Latin I) and this is also the SSIS default I think. However, there are also other encodings possible, such as UTF-8, but also Korean code pages, Chinese ones, Russian ones et cetera. The 1252 code page can handle normal western characters, but it can't display Chinese ones.
Unicode however, is an encoding standard that can deal with almost any character, so there is no need to specify a code, as it can handle everything.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
November 10, 2011 at 3:03 am
Thanks for quick reply.
We need it exactly in UTF-8 format. So will uncheck "unicode" and select code page as "UTF-8". Hope it will work teh way we want.
Thanks,
Smith.
November 10, 2011 at 3:19 am
Joy Smith San (11/10/2011)
Thanks for quick reply.We need it exactly in UTF-8 format. So will uncheck "unicode" and select code page as "UTF-8". Hope it will work teh way we want.
Thanks,
Smith.
Allright. Post back if you encounter problems. Good luck!
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
November 10, 2011 at 3:29 am
Just one more thing.. is there any way to verify the format of our newly created CSV file. ?
Thanks.
November 10, 2011 at 4:39 am
You can easily check encoding with the free tool Notepad++.
If you cannot use this tool, open the CSV file in regular Notepad and click File > Save as.
In the Save As window, you should see the encoding at the bottom.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
November 10, 2011 at 5:35 am
Koen Verbeeck (11/10/2011)
You can easily check encoding with the free tool Notepad++.If you cannot use this tool, open the CSV file in regular Notepad and click File > Save as.
In the Save As window, you should see the encoding at the bottom.
Hi,
When I opened in Notepad and clicked 'Save As' it was showing the encoding as "UTF-8" at the botttom.
But when I installed and opened the .CSV in Notepad++, in the 'Encoding' menu "Encode in Ansi" is selected. I mean it's having black dot there.
confused now. Is it in UTF-8 or ANSI..? Pls help.
November 10, 2011 at 5:48 am
Strange. At my computer both tools indicate the same encoding if it is utf-8.
Try to get your hands on a hex editor. With that you can truly check the encoding.
http://codesnipers.com/?q=how-to-determine-text-file-encoding
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
November 11, 2011 at 12:46 am
Hi All,
Nothing worked fo rme. I tried all the options.
Hence am I asking the question once again.
Suppose I have a table with a single varchar column (eg. name varchar(10)).
and table is having 100 rows.
I want to create an SSIS project to get this data in .csv file with UTF-8 format .
Can anyone tell me the steps to do the same, one by one.
Thanks in advance.
November 11, 2011 at 7:49 pm
..Awaiting for responses.. Pls help.
Thanks.
November 12, 2011 at 4:11 am
If you set the flat file connection manager as utf-8, it should be utf-8. So there is probably a misconfiguration somewhere.
Check your package and make sure the resulting flat file is utf-8 or not.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 15 posts - 1 through 15 (of 17 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy