Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>In the SQL server 2008 R2 there will be Unicode compression, see <a href="http://blogs.msdn.com/sqlserverstorageengine/archive/2009/08/17/unicode-compression-in-sql-server-2008r2.aspx" rel="nofollow noreferrer">Unicode Compression in SQL Server 2008R2</a>. This will make the problem of storage space of nvarchar vs. varchar largely a problem of the past. You are on SQL 2005 still, but you should <a href="http://c2.com/cgi-bin/wiki?ProgramInTheFutureTense" rel="nofollow noreferrer">program in the future tense</a>.</p> <p>The question of varchar vs. nvarchar is only one facet of the problem. The other facet is the enforcement of proper collation (needed for nvarchar just as much as for varchar). Since columns cannot have multiple collations, the common solution is to separate the data into string tables for each language, where columns are declared with the appropiate collation for each language used.</p> <p><strong>Update</strong></p> <p>There is a lengthy discussion of SQL Server 2005 international data at <a href="http://msdn.microsoft.com/en-us/library/bb330962(SQL.90).aspx" rel="nofollow noreferrer">International Features in Microsoft SQL Server 2005</a>. BTW, comments like 'just use UTF-8' are just missing the point. SQL Server stores nvarchar data encoded as UCS-2 and that's it, period. You can store XML data as UTF-8 or UTF-16, but no sane database person would recommend using XML to store your strings.</p> <p>Also while you may get away with an <em>encoding</em> like 1252, you will not get away so easily with a single collation. Specially since you have Spanish as a requirement and Spanish collations are notoriously problematic. For example your Spanish speaking users will expect 'Chiapas' to sort after 'Colima', but the Latin collation will sort 'Colima' after 'Chiapas', see <a href="http://msdn.microsoft.com/en-us/library/ms187582.aspx" rel="nofollow noreferrer">Working with Collations</a>. Other problems will appear at comparison, where names that are different may be compared to be equal, again due to the wrong collation choice.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload