Let us learn how to store non-English Characters in SQL Server tables. You will learn in this video the major difference between VARCHAR and NVARCHAR.
I often get to chance to attend as a panelist of SQL Server Interviews. I often see user getting confused when any of the following two questions are being asked them.
Q1: How to store non-English strings in SQL Server tables?
Q2: What is the major difference between VARCHAR and NVARCHAR in SQL Server?
Well, the answer is very simple and easy. I have discussed this in detail in the video attached here.
To demonstrate multiple languages, I have spoken about multiple languages in this video as well. Let me know if you can recognize the languages which I am speaking in this video.
You can download the scripts used in this video from this blog post: SQL SERVER – Storing a Non-English String in Table – Unicode Strings
I would like to get your feedback about the following two topics about this video.
Feedback Q1: Do you like the presentation of the topic?
Feedback Q2: What is your preferred length of this video? a) Longer b) Sorter c) Just about right.
Well, that’s it for today for discussing Storing Non-English Characters. If you like what you see, do not forget to subscribe to my YouTube Channel.
Published by Pinal Dave on SQLAuthority. More of my work at pinaldave.com.
2 Comments. Leave new
Starting with SQL2019, you have the ability to choose an UTF-8 characterset, which makes nvarchar obsolete and it’s less space-consuming. A customer of my company wants to have both English, Chinese and Russian characters in his database and we combined the upgrade to SQL 2019 with an UTF-8 characterset migration.
More non-english videos, please! I know subtitling can be tiresome, but from time to time may you use your native lang?