SQL Server Customer Advisory Team - SQL Server Best Practices

Enabling SQL Server customers to navigate the most challenging frontiers of large scale data management.

Whitepapers

Best Practices for Migrating Non-Unicode Data Types to Unicode

SQL Server Best Practices Article

Published: January 21, 2008
Writer: Kohei Ueda
Technical Reviewers: Paul Mestemaker, Michael Redman, Wanda He, Juergen Thomas, Burzin Patel, Peter Scharlock, Michael Wang, Fernando Caro, Sanjay Mishra, Osamu Hirayama, Akio Jose

The database system in a company that is growing internationally must support multilingual characters in tables with Unicode data types. Existing databases that support only non-Unicode information must be migrated from non-Unicode data type to Unicode data type. This paper summarizes best practices for migrating database systems from non-Unicode to Unicode data type.

For more information, please refer to the Best Practices for Migrating Non-Unicode Data Types to Unicode whitepaper.

Published Jan 22 2008, 11:25 PM by SanjayMishra

Filed under: Performance, SQL, design, Unicode, Data Types, Collations

Comments

	Tom Towns said: When I click the link for downloading the whitepaper I get a download of the paper on Database Mirroring and Log Shipping Working Together instead of the Best Practices for Migrating Non-Unicode Data Types to Unicode. Can you please take a look at this? Thanks, Tom February 11, 2008 2:36 PM
	SanjayMishra said: Hi Tom, Thanks for your comment. I apologize for the wrong link. The link is corrected now. Sanjay February 11, 2008 4:12 PM
	SQL Server 開発チームブログ said: マイクロソフトの植田です。ご無沙汰しております。少し間が開いてしまいましたが、引き続きSQL Serverのベストプラクティスに関して情報発信していきたいと思います。今回は SQL Server における、非ユニコードデータ型をユニコードデータ型に変換する際のベスト・プラクティスをご紹介させて頂きます。具体的には、 April 30, 2008 4:07 AM
	koheiu said: The comment above is a trackback from a blog providing information about latest release, best practices and tools of SQL Server in Japanese. Please come and see if you are familiar with both Japanese and SQL server. Thanks, Kohei June 25, 2008 9:36 PM