Results 1 to 4 of 4
  1. #1
    Join Date
    Mar 2004
    Location
    chennai
    Posts
    25

    Unanswered: simple Q' about Data type

    hi,

    when to use varchar and
    when to use Nvarchar....

    could any one tell please....

    thanks
    Sakthi

  2. #2
    Join Date
    Jan 2003
    Location
    India
    Posts
    523

    Re: simple Q' about Data type

    Originally posted by j_sakthivel
    hi,

    when to use varchar and
    when to use Nvarchar....

    could any one tell please....

    thanks
    when you have non unicode data use varchar
    and when u are dealing with unicode data use nvarchar.

  3. #3
    Join Date
    Mar 2004
    Location
    chennai
    Posts
    25
    thanks harshal,

    but, unicode means tell any one example.
    Sakthi

  4. #4
    Join Date
    Jan 2003
    Location
    India
    Posts
    523
    Originally posted by j_sakthivel
    thanks harshal,

    but, unicode means tell any one example.
    From BOL:
    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™ 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.



    Also check out this site for more information on unicode :


    http://www.unicode.org/standard/WhatIsUnicode.html

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •