|
|
Posted by rhaazy on 06/02/06 18:11
thanks for all your help, the problem is no more.
Erland Sommarskog wrote:
> rhaazy (rhaazy@gmail.com) writes:
> >> OK, use the text data type then. The important issue is that you should
> >> not pass it as Unicode, that is ntext/nvarchar.
> >
> >
> > Will this cause any other problems with my XML, are there any
> > characters that aren't included in the TEXT type that are in NTEXT?
>
> Yes and no. Text is 8-bit only, thus normally you have access to one
> code page. However, you are passing UTF-8, so you have access to the
> same characters as with ntext.
>
> Note, though, that the only context where SQL Server understands UTF-8 is
> an XML document which has this encoding. You can store UTF-8 data in
> text or varchar columns, but outside XML operations, SQL server will
> treat the data as eight bit text, meaning to that sorting will not be
> as desired, len() may return an incorrect result etc.
>
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|