why microsoft using nvarchar/nchar instead of varchar/char

  • can anybody please explain me why microsoft using nvarchar nchar instead of varchar/char in northwind database and pubs database. I know if a column holds unicode data you should use nvarchar or nchar but for me all those tables in northwind/pubs are not unicode data. but still why microsoft settled for nchar/nvarchar.

  • For portability and storing International Data...from BOL..

    "International Data and Unicode

    Storing data in multiple languages within one database is difficult to manage when using only character data and code pages. It is difficult to find one code page for the database that can store all the required language-specific characters. It is also difficult to ensure the proper translation of special characters when being read or updated by different clients running various code pages. Databases that support international clients should always use Unicode data types instead of non-Unicode data types.

    For example, a database of customers in North America has to handle three major languages:

    Spanish names and addresses for Mexico.

    French names and addresses for Quebec.

    English names and addresses for the rest of Canada and the United States."







    **ASCII stupid question, get a stupid ANSI !!!**

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply