Character is changed from ≤ to =

Question

When I run the following stored procedure with the exec statement following it, the ≤ character is changed to =
Thanks for any suggestions to fix this.
Create PROCEDURE [dbo].[XML_ADDJQTEST]
@objectName
varchar(255),
@xml Text,
@nodeType
varchar(10),
@retval
int output
AS
INSERT INTO dbo.XML
object_Name,
xml,
nodeType
VALUES
@objectName,
@xml,
@nodeType
Select @retval=@@ROWCOUNTCreate PROCEDURE [dbo].[XML_ADDJQTEST]
@objectName
varchar(255),
@xml varchar(500),
@nodeType
varchar(10),
@retval
int output
AS
INSERT INTO dbo.XML
object_Name,
xml,
nodeType
VALUES
@objectName,
@xml,
@nodeType
Select @retval=@@ROWCOUNT
exec XML_ADDJQTEST @objectName = 'jqtest2', @xml = '<test>(ADT ≤ 400)</test>',  @nodeType= 'short', @retVal=''

Answer 1

>I am managing a system that uses this 'xml' table, with the xml field that is actually 'text', and it is a very critical part of the system.
>How difficult do you think it would be to make this change to this table?
1) Identify all the code that accesses this table, so you know what to test after making the change.
2) Decide if you want to use NVARCHAR(MAX) or XML
If you store it as XML then you can query inside the document with TSQL, but you have to parse the document on load.  So useful, but more expensive on load. 
3) Decide if you want to store the XML documents inline in the table, or push them entirely off row.
use
exec sp_tableoption 'xml', 'large value types out of row', 1
To force the documents entirely off row, leaving only a pointer on the row.  This gives you more rows per page, improving the performance of queries that hit this table but don't need to read the document body, but requires an extra IO to read small
documents which would otherwise be stored inline in the row.
Change the data type.  This is simple, but can be expensive if the table is very large.  eg
alter table XML alter column xml nvarchar(max)
David
David http://blogs.msdn.com/b/dbrowne/