Showing posts with label accent-sensitive. Show all posts
Showing posts with label accent-sensitive. Show all posts

Sunday, March 11, 2012

Accent-sensitive

My SQL is instaled with CAse-Insensitive and Accent-Insensitive, but when I
search some thing with Full Text Search the result is diferent using accent
or not.
My server is a Windows 2000 server and MS SQL Server 2000.
Tia
Marcos Stabel
Unfortunately SQL FTS is not Accent Sensitive, ie a search on a word like cafe will not match with a search on a word like cafe (with an accent).
You have to trap for words which could be accented in your search phrase and then expand them into a search on the accented and unaccented versions of this work.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
|||I Think you want to say the SQL FTS is not Accent Insensitive. If it was Accent Insensitive, Marco would have no problem !
|||Are you sure, Hilary, there is no way to change the SQL server'catalog sensitivity ?
|||Accent sensitive means that when I query on cafe, in a table like this
select * from TableName where col1='cafe' I will not get rows returned to
the accented version of cafe.
Accent insensitive means that I will.
With SQL FTS, the tokens found in your columns you are full text indexing
are stored as unicode, so a cafe is a different unicode sequence than the
accented version of cafe.
You can select how SQL Server treats accents, but not MSSearch, which is the
engine which does your searching in SQLFTS.
So to be totally correct - SQL FTS is accent sensitive or not accent
insensitive. Thanks for the correction.
"Syl20" <anonymous@.discussions.microsoft.com> wrote in message
news:88DDAA02-A424-4FE4-9E3A-F797ED2D543B@.microsoft.com...
> I Think you want to say the SQL FTS is not Accent Insensitive. If it was
Accent Insensitive, Marco would have no problem !
|||There is no way to change the accent handling capabilities of SQL Server
FTS, other than expanding your search phrase to search on the accented and
unaccented versions of the phrase.
"Syl20" <anonymous@.discussions.microsoft.com> wrote in message
news:F2EEC4B5-67E6-4AFB-B2D9-700490242FC5@.microsoft.com...
> Are you sure, Hilary, there is no way to change the SQL server'catalog
sensitivity ?
|||Yes, you are right.
This possibility will be available with Microsoft SQL-Server 2005 ("Yukon")
|||Syl20,
Yes, this feature will be in Microsoft SQL-Server 2005 ("Yukon"), for
example:
USE Adventureworks
GO
CREATE FULLTEXT CATALOG Employee_FTC WITH ACCENT_SENSITIVITY = ON
CREATE FULLTEXT INDEX ON Employee(FirstName, LastName, Title, EmailAddress)
KEY INDEX PK_Employee_EmployeeID ON Employee_FTC
Regards,
John
"Syl20" <anonymous@.discussions.microsoft.com> wrote in message
news:A9DEF7CE-13B2-49E7-86ED-2A9B759B13D3@.microsoft.com...
> Yes, you are right.
> This possibility will be available with Microsoft SQL-Server 2005
("Yukon")

Accent-insensitive HELP.

Hello,
I need to change for an old db (SQL 2K) the property Accent-sensitive to Accent-insensitive and I don't know how .
If someone has a solution I needs some help please.
Thank you.Example: on a database named Products with the language French

ALTER DATABASE Products

COLLATE French_CI_AI

the CI_AI tells it to be Case Insensitive and Accent Insensitive|||Originally posted by Memnoch1207
Example: on a database named Products with the language French

ALTER DATABASE Products

COLLATE French_CI_AI

the CI_AI tells it to be Case Insensitive and Accent Insensitive

I try but doesn't work .
The script : ALTER DATABASE Products COLLATE French_CI_AI
return : The command(s) completed successfully.

but my select with : WHERE id = 'abcd' and WHERE id = 'abcde' is different .

?!|||Changed default database collation only.
You must alter all tables in you database.

A,Change collation of table columns by EM.

B,Faster would be
1.Generate script for all database by EM to text file without Generate drop existing option.
2.Open this file in notepad
3.Replace collation strings French_CI to French_CS (use your collation)
4.Copy create database part to QA and change database name and run
5.Switch to new database
5.Copy create tables part to QA and run
6.Use DTS wizard to copy data from your old database
7.Copy all remaining code to QA and run
8.Switch your databases by sp_renamedb (old->bak,new->old)

Note that server can use different collation from database. TempDb uses collation of model.