Keith Sauvant (oecher7.z.ksau (AT) spamgourmet (DOT) com) writes:
Quote:
processing unicode data in MSSQL seems to require prefixing of all
constants in queries by a "N". That is not fun when it comes to unicode
enabling of big applications... |
In T-SQL all literals are typed, and string literals delimited by ''
are varchar. To get an nvarchar literal, you need N''.
This is not unique to T-SQL; in C++ "" refers to*a char[] literal, and to
get a wchar literal you need L"".
As for UTF-8, SQL Server does not support UTF-8 per se; the internal
storage format is UCS-2, and this is also used on the wire. However, a
good client API should hide this fact from you.
--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se
Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx