Re: Character Problems
From: John Kane (jt-kane_at_comcast.net)
Date: 01/06/05
- Next message: John Kane: "Re: Full text Search"
- Previous message: Hilary Cotter: "Re: Full text Search"
- In reply to: Esref DURNA: "Re: Character Problems"
- Next in thread: Esref DURNA: "Re: Character Problems"
- Reply: Esref DURNA: "Re: Character Problems"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 5 Jan 2005 18:43:03 -0800
Esref DURNA,
There is no need to use the Full-Text Indexing Wizard as you can use T-SQL
code to accomplish the same thing, for details see:
http://spaces.msn.com/members/jtkane/PersonalSpace.aspx?_c01_blogpart=blogmgmt&_c=blogpart
Specifically, you can use the following SQL code and change the code to
reference your database and table and then change the nText column to use
the Neutral "Language for Word Breaker":
use pubs
go
IF OBJECTPROPERTY ( object_id('pub_info'),'TableHasActiveFulltextIndex') = 1
BEGIN
print 'Table pub_info is Full-Text Enabled, dropping Full-Text Index &
Catalog...'
EXEC sp_fulltext_table 'pub_info', 'drop'
EXEC sp_fulltext_catalog 'PubInfo', 'drop'
END
ELSE IF OBJECTPROPERTY (
object_id('pub_info'),'TableHasActiveFulltextIndex') = 0
BEGIN
print 'Table pub_info is NOT Full-Text Enabled, creating FT Catalog,
Index & Activating...'
EXEC sp_fulltext_catalog 'PubInfo', 'create'
EXEC sp_fulltext_table 'pub_info', 'create', 'PubInfo', 'UPKCL_pubinfo'
-- add 0 as the last parameter for the Neutral wordbreaker.
EXEC sp_fulltext_column 'pub_info', 'pub_id', 'add', 0
EXEC sp_fulltext_column 'pub_info', 'pr_info', 'add', 0
EXEC sp_fulltext_table 'pub_info', 'activate'
END
go
Furthermore, you should insure that you are using the "N prefix" when
referencing text and data in the Unicode datatypes of nText, nChar and
nVarchar, see KB article 239530 (Q239530) "INF: Unicode String Constants in
SQL Server Require N Prefix"
http://support.microsoft.com/default.aspx?scid=kb;en-us;239530 for more
details.
Thanks,
John
-- SQL Full Text Search Blog http://spaces.msn.com/members/jtkane/ "Esref DURNA" <EsrefDURNA@discussions.microsoft.com> wrote in message news:E3E505F6-756D-4209-8644-7803497690E4@microsoft.com... > The user could write "Izmir" or "izmir" > These queries gets different number of results. > We are using nText . > SQLserver Fulltext engine does not support turkish language so we cant > choise it by the wizard. > > Thanks for your help > > "Hilary Cotter" wrote: > > > What happens if you use the neutral word breaker? I take it you are either > > using nvarchar, nchar, or nText; or using the Turkish collation. > > > > Also, what is the error you are getting? Are you getting an error message, > > or instead are you not getting any results? > > > > -- > > Hilary Cotter > > Looking for a SQL Server replication book? > > http://www.nwsu.com/0974973602.html > > "Esref DURNA" <EsrefDURNA@discussions.microsoft.com> wrote in message > > news:268F7F6A-41AD-4FFC-AB76-9FCC7510A4F5@microsoft.com... > > > The spesific characters of turkish alphabets ->>igüsöç > > > couse problems while searching in the Fulltext search. > > > The letter i is "I" in the uppercase in our alphabet which is equal to the > > > English letter "I" > > > The the other lets does not exists in english alphabet. > > > so the turkish letters always couse problem for us. > > > > > > Thanks for any sugestions from now. > > > > > > > > >
- Next message: John Kane: "Re: Full text Search"
- Previous message: Hilary Cotter: "Re: Full text Search"
- In reply to: Esref DURNA: "Re: Character Problems"
- Next in thread: Esref DURNA: "Re: Character Problems"
- Reply: Esref DURNA: "Re: Character Problems"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
