Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!fu-berlin.de!uni-berlin.de!news.dfncis.de!not-for-mail
From: Keith Sauvant <oecher7.z.ksau@spamgourmet.com>
Newsgroups: comp.databases.ms-sqlserver,microsoft.public.de.sqlserver,comp.lang.php
Subject: UTF-8 in MSSQL
Followup-To: comp.databases.ms-sqlserver
Date: Thu, 08 Sep 2011 17:33:04 +0200
Lines: 10
Message-ID: <9cs5hfF6q1U1@mid.dfncis.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: news.dfncis.de atMfTr8fCnJP7I/TQNmLEw0Nlf6g4XcB7RdAQwHlTCSew+qW5BDVAaRUn8
Cancel-Lock: sha1:P4uiCGcxj+rM4zcJys983RLQtn4=
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
Xref: x330-a1.tempe.blueboxinc.net comp.databases.ms-sqlserver:653 comp.lang.php:3099

Hi,

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...

Is there a way around that?

Thank you in advance
Keith