Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 Full-Text search and the accent insensitive

Author  Topic 

ig25asya
Starting Member

2 Posts

Posted - 2004-07-09 : 11:48:31
Found this topic dated 10/01/2001 with no replies.
Here is what it looked like:
Posted - 10/01/2001 : 10:17:11

----------------------------
jan willem writes "Hi, I am using SQL Server 2000, Windows 2000 and have the collation for my database set to SQL_Latin1_General_CP850_CI_AI. I would like to search text data that contains accented words but I want my search to be accent insensitive. With my database collation set as above, using the "LIKE" keyword accomplishes what I desire. However, I would like to use full-text searching and the accent insensitive collation does not apply.
Has anyone had any luck with this? Is there a way to cast the full-text search predicate to a specific collation?
----------------------------

I'm looking for solution now too.
Did any one had to deal with such a problem before? Any leads/references, please.

ig25asya
Starting Member

2 Posts

Posted - 2004-07-09 : 13:58:06
looks that if found an answer. It's not possible in MSSQL 2000 without use of some other product.
here is the reference to the paper
Microsoft Support WebCasts
Microsoft SQL Server 2000: Full-Text Search and Service Pack 3
January 9, 2003:
http://support.microsoft.com/default.aspx?scid=%2fservicedesks%2fwebcasts%2fen%2fwc010903%2fwct010903.asp

...
Otto: Is there any way to have accent insensitive searches? Currently I have to preprocess the search to normalize foreign-accented characters.

Rashid: As far as I know, this has not changed on SP3. I remember reading a question that another customer submitted earlier and, as far as I know, it has not changed as part of SP3, but I think you can now do it on SP3. That will definitely be something that we could follow up and get a definite answer to because I cannot be 100 percent for sure right now.

Follow-up answer: This issue was not fixed in Service Pack 3.
...

Looks that this topic can be dropped
Go to Top of Page
   

- Advertisement -