Regarding korean noise file shipped with SQL server 2005

Vishesh,

If the noise word file were 0 bytes it would fail over to the default noise
word list, which is full of English words and characters. So, this is
providing Korean with no noise words, which will result in all words being
indexed.

Korean is supported in SQL Server 2005 and the Korean wordbreaker is one of
the few that was not modified for SQL Server 2008.

RLF


"Vishesh" wrote in message
newsF23BFDE-6A22-4D42-9B12-3AEB6521FCA4atmicrosoftdotcom...
> Hi,
>
> I am trying to add new stop words in the Korean language (noiseKOR.txt)
> noise file shipped with the SQL server 2005.This file is located at
> Microsoft
> SQL Server\MSSQL\FTDATA. The size of this file is 2 bytes and does not
> contain anything. In SQL server 2000 this file has same content as the
> English noise file. Other noise files have frequently used words according
> to
> there languages.
>
> Is Korean language supported for free text search in SQL server 2005 and
> this file is intentionally kept blank?
>
> Thanks in advance,
> Vishesh