SQL Server Reference Guide

Mar 28, 2003

␡

⎙ Print

< Back Page 169 of 365 Next >

If you’re looking for more up-to-date information on this topic, please visit our SQL Server article, podcast, and store pages.

Systems have often been designed to be used in a single country, in a single language, and for a single audience. But as the world matures, organizations are increasingly required to expand that audience to other locations. As this happens in the business, most DBAs and developers will be faced with the need to "Globalize" their systems.

The word "Globalize" means that your software systems should be flexible enough to deal with different time zones, money and date formats, and, not least of all, languages. In this tutorial I'll focus on dealing with the language components — I'll explain the other facets in another article.

The first question that comes to mind then, of course, is how to store more than one language at a time. We're all familiar with working on a system that has a particular language installed where we read the screen and type in information. And of course on a "client" system like this, it's easy to think about applications and ultimately data in a database that they access, in a single language. But the new requirements state that while you look at the screen in one language, someone on the other side of the world needs to look at data from that system in another language — the system is providing storage for both sets of users. How can we accomplish this?

As you're already aware (or can probably guess), computers deal in numbers — specifically in binary numbers. To oversimplify a bit, a computer is nothing more than a huge set of off and on switches. Those numbers get converted to whole numbers to store things like the screen coordinates of a pixel or the number associated with a letter on a keyboard. So when you press the letter "A" on keyboards manufactured for the English language, the keyboard sends electronic symbols that are converted to the binary number 1000001, or decimal 66 (it's different for a lower-case "a"). The computer (or more accurately the software running on the computer) deals with this number however it is supposed to. In the case of a database, the number is stored inside a database column or field.

This happens using the American Standard Code for Information Interchange codes, or ASCII. Most electronic equipment made in the US conforms to these codes. These 128+ number codes, which include 32 non-printable characters (for things like a carriage return or line feed) cover all of the letters of the English alphabet. But these codes don't cover other letters, so you can't use them to store characters other than English.

To fix this problem, another set of number-to-character mappings was invented, called "Unicode". Unicode contains far more choices for storage of the chapter-mappings, since it doesn't use numbers to represent characters directly, but instead uses encoding. Encoding is indeed a set of numbers, but it uses bits (ones and zeroes) to represent characters and states of characters. By setting a bit off or on, for instance, you can represent the "case" of a letter, saving an entire set of numbers to just represent the character itself. What this gets you is a substantially larger set of characters you can work with. Rather than storing only the letters of the English alphabet and a few other characters, you get more than 100,000 characters you can store! As an added bonus, the original ASCII numbers are seamlessly represented in the Unicode set, so everything just continues to work like it always has, at least for computers and electronics that used ASCII before.

All this comes at a cost, of course. It takes more space to store these extra characters, although not as much more as you might think. We'll come back to that in a moment.

Now that you understand how the encoding of the characters works, we can start working on how to use Unicode in a SQL Server system. This is the part that confuses a lot of people, and we should stop for a moment and talk about how the system will use Unicode.

SQL Server uses something called a collation, which is a set of character mappings. These characters are stored using a single byte representation, so you can get around 256 characters using one collation. The collations are selected when you install the server, and then you can select a collation (or code page) when you create a database. These collations define how characters are sorted and compared, based on a language specification and locale settings.

So, when you want to work with international data, you need to do a couple of things. First, check the server's collation (the Windows server collation, that is) where SQL Server will be installed. By default, the collation for SQL Server is set to the same as the operating system. In fact, any operations that depend on a particular collation, means that the particular collation needs to be present on the operating system as well.

Second, you need to decide how to deal with multi-language data. When you think about it, most of the time all you need to store for multiple languages are the characters — not numbers or dates. Because of that, Microsoft created the nchar (specific-length characters), nvarchar (variable-length characters), and nvarchar(max) (large variable-length characters) data types, in SQL Server 2005. In SQL Server 2000, you use the ntext data type instead of nvarchar(max).You can use these data types within a database to store the fields that you think might take input from multiple languages.

By the way, your applications will send these characters to your database. I've been asked before, "If I set a field to Unicode using one of these data types and I enter the word 'Hello', will it automatically translate it to another language, like 'Bonjour'?" The answer is no. although that would be pretty cool.

Using one of these Unicode types (distinguished by the "n" in front of the type name) uses twice as many bits (two, in fact) to store the data. That gives the system that sent the data the room for the character mapping, and identifies itself as Unicode data.

So you can see that you also need to be concerned about how much more storage you'll need with Unicode data. For one thing, you get half the amount of "width" in a text field. With standard char or varchar types you get 8000 characters in a single field — but with the nchar or nvarchar types you only get 4000.

Collations define the sort orders and comparisons of data. This is true even with Unicode data. Things won't automatically sort using another language just because the field is using a Unicode type. There is a special algorithm for dealing with sorting Unicode columns data, so you'll need to test the results of your code, and there will be a performance impact as well.

Just to make things a little more complicated, it is important to note that SQL Server 2000 and 2005 use the Unicode standard of UCS-2. There are actually several other Unicode standards, so you'll need to coordinate with the application owners to ensure they use the same one, or that you create a function or code shim to translate between UCS-2 and whatever the applications use.

We've only scratched the surface on Unicode data and data programming, and we haven't discussed the full impact of globalizing your applications and their data. Understanding these basics of Unicode is a good start. There are some references at the end of this overview that will help you explore this topic further.

InformIT Articles and Sample Chapters

Still using SQL Server 2000? There's more about the data types, including Unicode, in this free chapter.

Books and eBooks

Richard Gillam has a great practical guide to all this in his book, Unicode Demystified: A Practical Programmer’s Guide to the Encoding Standard.

Online Resources

Books Online for SQL Server 2005 largely holds true for 2000 as well, as far as Unicode data goes. You can find that reference here.

< Back Page 169 of 365 Next >

🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Privacy Notice

Overview

Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security

Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children

This site is not directed to children under the age of 13.

Marketing

Pearson may send or direct marketing communications to users, provided that

Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
Such marketing is consistent with applicable law and Pearson's legal obligations.
Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out

Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

As required by law.
With the consent of the individual (or their parent, if the individual is a minor)
In response to a subpoena, court order or legal process, to the extent permitted or required by law
To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
To investigate or address actual or suspected fraud or other illegal activities
To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links

This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020

Email Address