Shakespeare and storing Unicode characters
Posted
by John Paul Cook
on SQL Blog
See other posts from SQL Blog
or by John Paul Cook
Published on Wed, 26 Jun 2013 02:21:00 GMT
Indexed on
2013/06/26
4:25 UTC
Read the original article
Hit count: 244
Filed under:
This post is about the political issues involved with using multiple languages in a global organization and how to troubleshoot the technical details. The CHAR and VARCHAR data types are NOT suitable for global data. Some people still cling to CHAR and VARCHAR justifying their use by truthfully saying that they only take up half the space of NCHAR and NVARCHAR data types. But you’ll never be able to store Chinese, Korean, Greek, Japanese, Arabic, or many other languages unless you use NCHAR and NVARCHAR...(read more)
© SQL Blog or respective owner