Diffrence between text and ntext | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Diffrence between text and ntext

Hi all,
What is the Diffrence between the text and ntext? Thanks & Regards,
Unicode (ntext) has the capability to store characters from all languages, while text typically uses a local code page and can only use local characters. SQL Server uses 2 bytes per character for n-type text columns, while the not-n-type columns use 1 (at least for latin-based languages).
SQL-Server-Performance.com All postings are provided “AS IS” with no warranties for accuracy.

quote:Using Unicode Data
The Unicode specification defines a single encoding scheme for most characters widely used in businesses around the world. All computers consistently translate the bit patterns in Unicode data into characters using the single Unicode specification. This ensures that the same bit pattern is always converted to the same character on all computers. Data can be freely transferred from one database or computer to another without concern that the receiving system will translate the bit patterns into characters incorrectly. One problem with data types that use 1 byte to encode each character is that the data type can only represent 256 different characters. This forces multiple encoding specifications (or code pages) for different alphabets such as European alphabets, which are relatively small. It is also impossible to handle systems such as the Japanese Kanji or Korean Hangul alphabets that have thousands of characters. Each Microsoft® SQL Server#153; collation has a code page that defines what patterns of bits represent each character in char, varchar, and text values. Individual columns and character constants can be assigned a different code page. Client computers use the code page associated with the operating system locale to interpret character bit patterns. There are many different code pages. Some characters appear on some code pages, but not on others. Some characters are defined with one bit pattern on some code pages, and with a different bit pattern on other code pages. When you build international systems that must handle different languages, it becomes difficult to pick code pages for all the computers that meet the language requirements of multiple countries. It is also difficult to ensure that every computer performs the correct translations when interfacing with a system using a different code page. The Unicode specification addresses this problem by using 2 bytes to encode each character. There are enough different patterns (65,536) in 2 bytes for a single specification covering the most common business languages. Because all Unicode systems consistently use the same bit patterns to represent all characters, there is no problem with characters being converted incorrectly when moving from one system to another. You can minimize character conversion issues by using Unicode data types throughout your system.

To addup Frank’s post :
All Unicode data uses the same Unicode code page. Collations do not control the code page used for Unicode columns, only attributes such as comparison rules and case sensitivity. Unicode supports a wider range of characters and more space is needed to store Unicode characters
Satya SKJ
Microsoft SQL Server MVP
Writer, Contributing Editor & Moderator
This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.

Note, that if you are on SQL Server 2005 and do not intend to support SQL Server 2000 and below, that you should use (N)VARCHAR(MAX) instead of (N)TEXT. This data type is deprecated and will be removed in a future version. —
Frank Kalis
Microsoft SQL Server MVP
Contributing Editor, Writer & Forum Moderatorhttp://www.sql-server-performance.com
Thank you very much.