New Best Practices Whitepaper Published: The Impact of Changing Collations and of Changing Data Types from Non-Unicode to Unicode

When a business grows internationally, its database system must support multilingual characters in tables. Businesses that previously needed to manage only non-Unicode information must now support database tables that include non-Unicode data types such as CHAR or VARCHAR. As the business grows internationally, it must alter its database system to support Unicode data types. It may also need databases that have different collations across several servers.

 

https://download.microsoft.com/download/d/9/4/d948f981-926e-40fa-a026-5bfcf076d9b9/SQL_bestpract_CollationChange.docx

Comments

• Anonymous
  December 06, 2007
  PingBack from http://msdnrss.thecoderblogs.com/2007/12/06/new-best-practices-whitepaper-published-the-impact-of-changing-collations-and-of-changing-data-types-from-non-unicode-to-unicode/

• Anonymous
  December 06, 2007
  Did you see the post at blogs.msdn.com

• Anonymous
  September 10, 2008
  <p>Sometimes you need to change the collation of a database after you have created it and populated it with objects and data. So how do you change the collation?</p> ...