Due to some massive confusion between Michael Kung, myself, and several
people on the SQL Server team, the incorrect statement was made that SQL
Server 2000 supports UTF-16 and is surogate aware. This is NOT true.
SQL Server 2000, like SQL Server 7.0, supports UCS-2. As such, it is
surogate safe. However, it does not recognize surrogate pairs as characters
and there is nothing within SQL Server or any of its tools that will do
anything more than properly store the data (as UCS-2 can do).
You may be a purist who believes that any program that will unknowingly
corrupt a surrogate pair is not "safe". If so, I guess the term "surrogate
neutral" or "surrogate tolerant" could be used. :-)
Sorry for the confusion on this issue.
Trigeminal Software, Inc.
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:21:13 EDT